lookup-ransomwarelive
Skill35 starsChanged 47 days agoMITView on GitHub
Use when you need to check whether an organisation/domain has been claimed by a ransomware group, profile a specific ransomware group (TTPs, leak-site infra, IOCs, YARA), or aggregate ransomware victim claims by country/sector/timeframe. Backed by ransomware.live's leak-site scrapes — 27k+ victims across 330+ groups. Commonly invoked by /domain-investigation, /ransomware-ecosystem, /threat-actor-profiling, and detection-engineering workflows. Reads $RANSOMWARE_LIVE.
In this repository79 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- abuseipdb-apiSkill
- achSkill
- campaign-trackingSkill
- carding-financial-fraudSkill
- censys-apiSkill
- china-cyber-espionageSkill
- claim-extractionSkill
- confidence-levelsSkill
- control-coverage-mappingSkill
- crowdstrike-apiSkill
- cti-hyperloopSkill
- cti-orchestratorSkill
- cti-setupSkill
- darkweb-collectionSkill
- devils-advocacySkill
- domain-investigationSkill
- dprk-cyber-espionageSkill
- feedback-loopsSkill
- greynoise-apiSkill
- hacktivismSkill
- hash-investigationSkill
- horizon-scanningSkill
- indicator-pivotingSkill
- infostealersSkill
- initial-access-brokersSkill
- intelligence-sharingSkill
- intelligence-writingSkill
- ioc-enrichment-workflowSkill
- ioc-exportSkill
- ip-investigationSkill
- iran-cyber-espionageSkill
- key-assumptions-checkSkill
- kql-writingSkill
- likelihood-languageSkill
- lookup-abuseipdbSkill
- lookup-censysSkill
- lookup-crowdstrikeSkill
- lookup-greynoiseSkill
- lookup-liberty91Skill
- lookup-mispSkill
- lookup-openctiSkill
- lookup-otxSkill
- lookup-reversinglabsSkill
- lookup-sentinelSkill
- lookup-shodanSkill
- lookup-urlscanSkill
- lookup-virustotalSkill
- malware-analysisSkill
- maturity-assessmentSkill
- mitre-attackSkill
- osint-methodologySkill
- otx-apiSkill
- phishing-social-engineeringSkill
- pir-managementSkill
- quality-controlSkill
- quality-of-information-checkSkill
- ransomware-ecosystemSkill
- reversinglabs-apiSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 100
All commands accept --dry-run (preview the request without spending quota) and --insecure (TLS bypass — rarely needed).
- Very specific: line 145
Default for /score-source: B2 (usually reliable, probably true).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
lookup-ransomwarelive
Queries ransomware.live's PRO API for victim claims, group profiles, IOCs, YARA rules, ransom notes, negotiation chats, and CSIRT contacts. Retrieval only — the invoking skill or agent reasons about the result. Note that leak-site claims are claims, not confirmed breaches (see Source reliability below).
When to invoke
- An investigated domain or organisation should be checked against ransomware leak-site claims
- Profiling a ransomware group — pull description, TTPs, tools, vulnerabilities, leak-site
.onioninfrastructure - Sector- or country-level ransomware briefing (e.g., "all NL victims claimed in 2026")
- Detection engineering for a specific group — fetch its public YARA rules + IOC dump
- Updating the
/ransomware-ecosystemknowledge cell with the current top-N groups by victim count - Incident response: looking up a country's CSIRT/CERT contact list
Do NOT invoke for:
- General malware classification — use
/lookup-virustotal - Confirming whether a specific incident actually occurred — leak-site claims are unverified by default
- Initial-access vector intelligence — that's not on leak sites; chain
/initial-access-brokersinstead
How to invoke
Single Python CLI (stdlib only — no install).
Sanity checks
python3 tools/clis/ransomwarelive.py validate # check the API key
python3 tools/clis/ransomwarelive.py stats # global totalsVictim lookups
# Free-text search across victim names + descriptions
python3 tools/clis/ransomwarelive.py search --q "acme corp"
# Targeted filters (combine freely)
python3 tools/clis/ransomwarelive.py search --country NL --limit 10
python3 tools/clis/ransomwarelive.py search --sector Healthcare --country US
python3 tools/clis/ransomwarelive.py search --group lockbit3 --limit 5
# Last 100 claims globally (newest first)
python3 tools/clis/ransomwarelive.py recent --limit 20
# Single victim detail by ransomware.live id
python3 tools/clis/ransomwarelive.py victim "QksgR3JvdXBAYWtpcmE="Group intelligence
# All 330+ groups, sorted by victim count
python3 tools/clis/ransomwarelive.py groups --limit 20
# Profile of a specific group — description, TTPs, tools, leak-site URLs, etc.
python3 tools/clis/ransomwarelive.py group-profile lockbit3
# Lighter group detail
python3 tools/clis/ransomwarelive.py group lockbit3Defensive intel
# IOC dump (md5, ip, etc.) — all groups
python3 tools/clis/ransomwarelive.py iocs
# Per-group IOCs
python3 tools/clis/ransomwarelive.py iocs lockbit3
# YARA rules — all groups, or per group
python3 tools/clis/ransomwarelive.py yara
python3 tools/clis/ransomwarelive.py yara lockbit3 # full rule content
# Ransom note samples
python3 tools/clis/ransomwarelive.py ransomnotes lockbit3
# Negotiation chat logs (if available for that group)
python3 tools/clis/ransomwarelive.py negotiations lockbit3Context
python3 tools/clis/ransomwarelive.py press # recent press mentions
python3 tools/clis/ransomwarelive.py press --all # full archive
python3 tools/clis/ransomwarelive.py sectors # valid sector filter values
python3 tools/clis/ransomwarelive.py csirt NL # CSIRT contacts for a countryAll commands accept --dry-run (preview the request without spending quota) and --insecure (TLS bypass — rarely needed). The CLI exits 2 if RANSOMWARE_LIVE is unset (not in dry-run); report missing key, do not fabricate.
Quota
PRO tier: 3,000 calls/day with burst allowed. Each subcommand is one HTTP call. Use --dry-run if scoping a batch.
Pivots
- From
/domain-investigationor/ip-investigation→search --q <orgname>to check if the domain's owner has been claimed - From
/ransomware-ecosystemknowledge cell →groups --limit 30for current top-N +group-profilefor each - From
/threat-actor-profiling(ransomware group target) →group-profile <name>is the primary feed; chainiocs,yara,negotiationsfor depth - From
/sigma-writing//yara-writing→yara <group>returns existing community rules to start from - Country-scoped briefing →
search --country <CC>, thencsirt <CC>for IR contact list
Response format
Read commands return:
source: ransomware.live
operation: search | recent | victim | groups | group-profile | iocs | yara | ...
query_time: <ISO8601>
data:
<distilled response>For search and recent, data.victims[] is normalised to:
id: <ransomware.live id>
title: <victim name>
group: <ransomware group, e.g. lockbit3, akira>
country: <ISO-3166 alpha-2>
sector: <activity / sector>
discovered: <when ransomware.live scraped the post>
published: <when leak-site authored the post>
description: <criminal-written breach summary — treat as low credibility>
website: <victim website>
post_url: <leak-site post URL, often .onion>
permalink: <ransomware.live record URL>
screenshot: <leak-site screenshot, if archived>Source reliability (Admiralty default)
Default for /score-source: B2 (usually reliable, probably true).
Important credibility nuance:
| Field | Credibility | Why |
| Victim name, country, sector, dates, group attribution | 2 (probably true) | Corroborated by the leak-site post itself |
Breach description | 3–4 (possibly true → doubtful) | Written by criminals to coerce payment; routinely overstates volume/sensitivity/ongoing access |
| YARA rules, IOC lists | 2 (probably true) | Sourced from public researchers; cross-check before deploying |
A leak-site claim is a claim, not a confirmed breach. Many victims dispute or never publicly acknowledge. Some posts repackage older breaches under a new brand. Always frame downstream products with this caveat.
Operational notes
- Server returns full result sets, not pages.
search --country UShits the API once and returns ~8k victims.--limit Ntrims locally — narrow with filters (--group,--sector,--country) to keep responses small. group_nameis sometimes null in/victims/recentresponses — known API quirk; the value populates correctly insearchandvictimdetail.- The
descriptionfield can contain victim PII or stolen credentials — quote selectively in finished products; don't paste full responses into shared docs. - PRO endpoint is
api-pro.ransomware.live. The free unauthenticated endpoint (api.ransomware.live, 1 req/min) is not supported by this CLI.
Related skills
/ransomware-ecosystem— knowledge cell consuminggroups+group-profiledata/threat-actor-profiling— for ransomware-group profiles, thegroup-profileendpoint is the primary feed/yara-writing,/sigma-writing— start fromyara <group>output/lookup-virustotal,/lookup-otx— chain after pulling group IOCs to verify hashes/domain-investigation— pivots intosearch --q <orgname>for victim-status check/initial-access-brokers— complementary; ransomware.live doesn't track IAB activity/score-source,/apply-tlp,/confidence-language— apply rigor before publishing
See also
- Integration setup:
tools/integrations/ransomwarelive.md - Python CLI source:
tools/clis/ransomwarelive.py - API docs: https://api-pro.ransomware.live/docs
- Project: https://www.ransomware.live/
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

