Skip to main content
skill CX Codex

analyzing-ransomware-payment-wallets — Claude Code skill

The analyzing-ransomware-payment-wallets skill follows cryptocurrency payments after ransomware incidents, linking wallets, transactions, mixers, and exchange deposits for forensic analysis.

Apache-2.0 262 installs ★ 36,511 updated 2026-08-31

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-ransomware-payment-wallets -a claude-code
Open on GitHub

What analyzing-ransomware-payment-wallets does

The skill starts with a wallet address from a ransom note, retrieves its transaction history, and follows funds to downstream addresses. It helps identify consolidation wallets, peel chains, mixer activity, and exchange deposits, then organizes the findings into an attribution report.

Its workflow includes Python requests to blockchain.com and WalletExplorer.com, address checks, and wallet-cluster analysis. It requires Python 3.8+ with requests, json, and hashlib, plus access to blockchain explorer APIs. Chainalysis Reactor and OXT.me are listed as optional tools.

The workflow is passive and read-only against public blockchain data. It is not for intercepting payments or communicating with ransomware operators. Without blockchain explorer API access, the transaction history step cannot run.

What it helps with

  • extract a payment address from a ransom note
  • retrieve transaction history for a Bitcoin wallet
  • follow funds through mixers and exchanges
  • group related wallets into an infrastructure cluster
  • compile findings into an attribution report

Example prompts for the agent

  • Trace the funds from this ransom wallet and map every downstream address you can verify.
  • Check this address against blockchain.com and WalletExplorer.com, then summarize the wallet links.
  • Create an attribution report from these transactions and flag mixer or exchange destinations.

How to install analyzing-ransomware-payment-wallets

1Skills CLI (Vercel)

npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-ransomware-payment-wallets -a claude-code

2Manually: put the files in place

~/.claude/skills/analyzing-ransomware-payment-wallets/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/analyzing-ransomware-payment-wallets/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about analyzing-ransomware-payment-wallets

How do I install analyzing-ransomware-payment-wallets in Claude Code?

Run npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill analyzing-ransomware-payment-wallets -a claude-code, then check ~/.claude/skills/analyzing-ransomware-payment-wallets/SKILL.md.

What does analyzing-ransomware-payment-wallets do?

It examines cryptocurrency payments linked to ransomware, follows transaction paths, groups related wallets, and checks movement through mixers and exchanges.

What does this skill require?

You need Python 3.8+ with requests, json, and hashlib, along with access to blockchain explorer APIs. The workflow uses public blockchain data in read-only mode.

Source text

SKILL.md · Apache-2.0
---
name: analyzing-ransomware-payment-wallets
description: 'Traces ransomware cryptocurrency payment flows using blockchain analysis tools such as Chainalysis Reactor, WalletExplorer, and blockchain.com APIs, identifying wallet clusters and tracking fund movement through mixers and exchanges to support law enforcement attribution. Use when tracing ransomware bitcoin payments, performing cryptocurrency wallet forensics, or gathering blockchain threat intelligence on extortion payments.

  '
domain: cybersecurity
subdomain: ransomware-defense
tags:
- ransomware
- blockchain
- cryptocurrency
- forensics
- threat-intelligence
- bitcoin
version: 1.0.0
author: mahipal
license: Apache-2.0
nist_csf:
- PR.DS-11
- RS.MA-01
- RC.RP-01
- PR.IR-01
mitre_attack:
- T1657
- T1486
mitre_f3:
  version: '1.1'
  tactics:
  - monetization
  - stealth
  techniques:
  - id: F1018
    name: Convert to Cryptocurrency
    tactic: monetization
    source: f3
  - id: F1017
    name: Conversion to Physical Monetary Instruments
    tactic: monetization
    source: f3
  - id: F1017.001
    name: 'Conversion to Physical Monetary Instruments: Cash'
    tactic: monetization
    source: f3
  - id: F1047
    name: Transfer of funds
    tactic: monetization
    source: f3
  - id: F1045
    name: Structuring
    tactic: stealth
    source: f3
---

# Analyzing Ransomware Payment Wallets

## When to Use

- An organization has been hit by ransomware and the ransom note contains a Bitcoin or cryptocurrency wallet address that needs investigation
- Law enforcement or incident responders need to trace where ransom payments flowed after the victim paid
- Threat intelligence analysts are attributing ransomware campaigns by clustering payment infrastructure across incidents
- Investigators need to determine if a ransomware group is reusing wallet infrastructure across multiple victims
- Compliance or legal teams need evidence of fund flows for prosecution, sanctions enforcement, or insurance claims

**Do not use** this skill for live payment interception or to interact directly with ransomware operators. All analysis should be passive and read-only against public blockchain data.

## Prerequisites

- Python 3.8+ with `requests`, `json`, and `hashlib` libraries
- Access to blockchain explorer APIs (blockchain.com, WalletExplorer.com, Blockstream.info)
- Familiarity with Bitcoin transaction model (UTXOs, inputs, outputs, change addresses)
- Understanding of common obfuscation techniques (mixers, tumblers, peel chains, cross-chain swaps)
- Optional: Chainalysis Reactor license for enterprise-grade cluster analysis
- Optional: OXT.me for advanced transaction graph visualization

## Workflow

### Step 1: Extract Wallet Address from Ransom Note

Parse the ransom note to identify the payment address(es):

```
Common address formats:
  Bitcoin (P2PKH):   1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa  (starts with 1)
  Bitcoin (P2SH):    3J98t1WpEZ73CNmQviecrnyiWrnqRhWNLy  (starts with 3)
  Bitcoin (Bech32):  bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq (starts with bc1)
  Monero:            4... (95 characters, much harder to trace)
  Ethereum:          0x... (40 hex chars)
```

### Step 2: Query Blockchain Explorer for Transaction History

Retrieve all transactions associated with the wallet:

```python
import requests

def get_wallet_transactions(address):
    """Query blockchain.com API for address transactions."""
    url = f"https://blockchain.info/rawaddr/{address}"
    resp = requests.get(url, timeout=30)
    resp.raise_for_status()
    data = resp.json()
    return {
        "address": address,
        "n_tx": data.get("n_tx", 0),
        "total_received_satoshi": data.get("total_received", 0),
        "total_sent_satoshi": data.get("total_sent", 0),
        "final_balance_satoshi": data.get("final_balance", 0),
        "transactions": data.get("txs", []),
    }
```

### Step 3: Map Fund Flow and Identify Clusters

Trace outputs from the ransom wallet to downstream addresses:

```
Fund Flow Analysis:
━━━━━━━━━━━━━━━━━━
Victim Payment ──► Ransom Wallet ──► Consolidation Wallet
                                  ├─► Mixer/Tumbler Service
                                  ├─► Exchange Deposit Address
                                  └─► Peel Chain (sequential small outputs)

Key indicators:
  - Consolidation: Multiple ransom payments aggregated into one wallet
  - Peel chains: Sequential transactions with diminishing outputs
  - Mixer usage: Funds sent to known mixer addresses (Wasabi, Samourai, ChipMixer)
  - Exchange cashout: Deposits to known exchange wallets (Binance, Kraken hot wallets)
```

### Step 4: Cross-Reference with Known Wallet Databases

Check addresses against known ransomware infrastructure:

```python
# Check WalletExplorer for entity identification
def check_wallet_explorer(address):
    url = f"https://www.walletexplorer.com/api/1/address?address={address}&caller=research"
    resp = requests.get(url, timeout=30)
    data = resp.json()
    return {
        "wallet_id": data.get("wallet_id"),
        "label": data.get("label", "Unknown"),
        "is_exchange": data.get("is_exchange", False),
    }
```

### Step 5: Generate Attribution Report

Compile findings into a structured intelligence report:

```
RANSOMWARE WALLET ANALYSIS REPORT
====================================
Ransom Address:      bc1q...xyz
Family Attribution:  LockBit 3.0 (based on ransom note format)
Total Received:      4.25 BTC ($178,500 at time of payment)
Total Sent:          4.25 BTC (wallet fully drained)
Number of Payments:  3 (likely 3 separate victims)

FUND FLOW:
  Payment 1: 1.5 BTC → Consolidation wallet → Binance deposit
  Payment 2: 1.0 BTC → Wasabi Mixer → Unknown
  Payment 3: 1.75 BTC → Peel chain (12 hops) → OKX deposit

CLUSTER ANALYSIS:
  Related wallets: 47 addresses identified in same cluster
  Total cluster volume: 156.3 BTC ($6.5M USD)
  First activity: 2024-01-15
  Last activity: 2024-09-22
```

## Verification

- Confirm wallet address format is valid before querying APIs
- Cross-reference transaction timestamps with known incident timelines
- Validate cluster associations by checking common-input-ownership heuristic
- Compare findings against OFAC SDN list for sanctioned addresses
- Verify exchange attribution against multiple sources (WalletExplorer, OXT, Chainalysis)

## Key Concepts

| Term | Definition |
|------|------------|
| **UTXO** | Unspent Transaction Output; the fundamental unit of Bitcoin that tracks ownership through a chain of transactions |
| **Cluster Analysis** | Grouping multiple Bitcoin addresses believed to be controlled by the same entity using common-input-ownership and change-address heuristics |
| **Peel Chain** | A laundering pattern where funds are sent through many sequential transactions, each peeling off a small amount to a new address |
| **CoinJoin/Mixer** | Privacy techniques that combine multiple users' transactions to obscure the link between sender and receiver |
| **Common Input Ownership** | Heuristic that assumes all inputs to a single transaction are controlled by the same entity |

## Tools & Systems

- **Chainalysis Reactor**: Enterprise blockchain investigation platform with entity attribution and cross-chain tracing
- **WalletExplorer**: Free tool that clusters Bitcoin addresses and labels known services (exchanges, mixers, markets)
- **OXT.me**: Advanced Bitcoin transaction visualization with UTXO graph analysis
- **Blockstream.info**: Open-source Bitcoin block explorer with full API access
- **blockchain.com API**: Free API for querying Bitcoin address balances and transaction histories
- **OFAC SDN List**: U.S. Treasury sanctioned address list for compliance checking

© mahipal · Apache-2.0 · mukul975/Anthropic-Cybersecurity-Skills

Similar skills

All skills for Finance and business →
ransomware-response W4L33Dx ransomware-response is a Claude Code skill that orchestrates incident response during extortion attacks. Triggers when file encryption or ransomware activity is detected across the network. CX Codex +1 ★ 73repo stars use-developer-controlled-wallets circlefin The use-developer-controlled-wallets Claude Code skill helps build applications with Circle Developer-Controlled Wallets. It covers wallet creation, token transfers, message signing and smart contract calls. CX Codex +1 1,000installs raas-extortion-and-negotiation-triage W4L33Dx raas-extortion-and-negotiation-triage is a Claude Code skill that structures incident response during double-extortion ransomware attacks. Triggers when attackers claim data theft. CX Codex +1 ★ 73repo stars Boar blockchain MCP (basic) boar-network Boar blockchain MCP (basic) is an MCP server with 50 read-only tools for Bitcoin, Ethereum, and Mezo data. Add its URL to a client; no API key or setup is needed. CX Codex +1 6,463installs satoshidata — Bitcoin entity intelligence satoshidata The satoshidata — Bitcoin entity intelligence MCP server for Claude Code connects agents to Bitcoin chain intelligence, checks wallet risk signals, and monitors mempool activity without requiring an API key. CX Codex +1 4,144installs use-circle-wallets circlefin use-circle-wallets — a skill that picks between developer-controlled, user-controlled and modular Circle wallets, then hands implementation to the matching skill. CX Codex +1 1,000installs

From the same set152

The whole set →
exploiting-prototype-pollution-in-javascript The exploiting-prototype-pollution-in-javascript Claude Code skill checks JavaScript and Node.js apps for prototype pollution. It activates during reviews of object merges that accept user-controlled keys. CX Codex +1 267installs exploiting-template-injection-vulnerabilities exploiting-template-injection-vulnerabilities is a Claude Code skill for detecting and exploiting SSTI in Jinja2, Twig, Freemarker and other template engines during authorized pentests. CX Codex +1 266installs performing-web-cache-poisoning-attack performing-web-cache-poisoning-attack — a skill that walks an agent through cache poisoning checks: unkeyed headers and parameters that still end up in the cached page. CX Codex +1 264installs conducting-cloud-penetration-testing conducting-cloud-penetration-testing — a skill for running authorized penetration tests on AWS, Azure, and GCP cloud environments. CX Codex +1 263installs testing-for-xml-injection-vulnerabilities testing-for-xml-injection-vulnerabilities — a skill that walks an agent through XML injection testing: XXE, blind XXE, SSRF and XPath. Useful when the target parses XML somewhere in the request path. CX Codex +1 261installs exploiting-http-request-smuggling exploiting-http-request-smuggling — a skill that detects and exploits HTTP request smuggling caused by discrepancies in how front-end and back-end servers parse request boundaries. CX Codex +1 260installs performing-api-rate-limiting-bypass performing-api-rate-limiting-bypass — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode tests API protection against rate-limit circumvention. CX Codex +1 259installs collecting-open-source-intelligence collecting-open-source-intelligence is a Claude Code skill that connects public data on threat actors, domains, and infrastructure for passive reconnaissance and CTI reports. CX Codex +1 257installs

Project sponsors

Companies that keep this analytics open