1HEDP3c3zPwiqUaYuWZ8gBFdAQQSa6sMGw
Sign in to watch
Alert when money comes in or goes out, as soon as the transaction shows up.
Heavy use: more than 100 incoming or on-chain transactions. An analyst checked the attribution against a public source; the address was reused, and not every inflow is a ransom. Rule: uso_intenso@1.
Observable history
- Received
- 13.58613392 BTC
- Sent
- 13.58613392 BTC
- Balance
- 0 BTC
- Transactions
- 101
- First activity
- —
- Last activity
- 22 Mar 2022
Checked on 18 Nov 2026 · Source: chain
The source recorded 94 incoming transaction(s), totalling 13.59 BTC, from 04 Jul 2021 to 21 Jan 2022. (ransom_payments)
Transactions
The effect is the net change for the address: positive came in, negative went out.
| Date | txid | Effect on the address | Source |
|---|---|---|---|
| 22 Mar 2022 | 8e25cbfa96…239713a5 | -0.30735775 BTC | chain |
| 21 Jan 2022 | daf0a73d8d…2991c91f | +0.15615084 BTC | public ransom-payment tracker |
| 21 Jan 2022 | daf0a73d8d…2991c91f | +0.15615084 BTC | chain |
| 11 Jan 2022 | 0f01c09e11…916679af | +0.07199073 BTC | public ransom-payment tracker |
| 11 Jan 2022 | 0f01c09e11…916679af | +0.07199073 BTC | chain |
| 07 Jan 2022 | 112b345cbf…6b919f8e | +0.07921618 BTC | public ransom-payment tracker |
| 07 Jan 2022 | 112b345cbf…6b919f8e | +0.07921618 BTC | chain |
| 03 Jan 2022 | 5a1f2de4c1…290e71b7 | -0.47454932 BTC | chain |
| 27 Dec 2021 | fd5e64ce8b…afc6cd1d | +0.18765932 BTC | public ransom-payment tracker |
| 27 Dec 2021 | fd5e64ce8b…afc6cd1d | +0.18765932 BTC | chain |
| 27 Dec 2021 | fbaafd999f…f126960f | +0.0005 BTC | public ransom-payment tracker |
| 27 Dec 2021 | fbaafd999f…f126960f | +0.0005 BTC | chain |
| 14 Dec 2021 | 0b234ab8b5…0f871e2e | +0.18 BTC | public ransom-payment tracker |
| 14 Dec 2021 | 0b234ab8b5…0f871e2e | +0.18 BTC | chain |
| 14 Dec 2021 | 46d0eb0a64…f78dfc77 | +0.001 BTC | public ransom-payment tracker |
| 14 Dec 2021 | 46d0eb0a64…f78dfc77 | +0.001 BTC | chain |
| 03 Dec 2021 | d98546302f…3fe8cb56 | +0.10539 BTC | public ransom-payment tracker |
| 03 Dec 2021 | d98546302f…3fe8cb56 | +0.10539 BTC | chain |
| 02 Dec 2021 | e4c35480c4…95bbe8d6 | -1.95350281 BTC | chain |
| 26 Nov 2021 | be5818d655…34d7e336 | +0.221 BTC | public ransom-payment tracker |
| 26 Nov 2021 | be5818d655…34d7e336 | +0.221 BTC | chain |
| 25 Nov 2021 | d03f6c4dae…493438f6 | +0.25916675 BTC | public ransom-payment tracker |
| 25 Nov 2021 | d03f6c4dae…493438f6 | +0.25916675 BTC | chain |
| 23 Nov 2021 | d11f1eb3f1…fca7bbdc | +0.15871906 BTC | public ransom-payment tracker |
| 23 Nov 2021 | d11f1eb3f1…fca7bbdc | +0.15871906 BTC | chain |
| 22 Nov 2021 | c6185268d5…bdedc147 | +1.314617 BTC | public ransom-payment tracker |
| 22 Nov 2021 | c6185268d5…bdedc147 | -1.0188643 BTC | chain |
| 22 Nov 2021 | 43a6a81c82…33de0a4e | +0.0340091 BTC | public ransom-payment tracker |
| 22 Nov 2021 | 43a6a81c82…33de0a4e | +0.0340091 BTC | chain |
| 21 Nov 2021 | 1c4dcc06a3…e23f31e4 | +1.0195 BTC | public ransom-payment tracker |
| 21 Nov 2021 | 1c4dcc06a3…e23f31e4 | +1.0195 BTC | chain |
| 16 Nov 2021 | 250681b51b…73ed926a | +0.10734264 BTC | public ransom-payment tracker |
| 16 Nov 2021 | 250681b51b…73ed926a | +0.10734264 BTC | chain |
| 14 Nov 2021 | e806836243…3fd78824 | +0.185569 BTC | public ransom-payment tracker |
| 14 Nov 2021 | e806836243…3fd78824 | +0.185569 BTC | chain |
| 12 Nov 2021 | 0e05bfdf4a…6e0f082c | +0.23389 BTC | public ransom-payment tracker |
| 12 Nov 2021 | 0e05bfdf4a…6e0f082c | +0.23389 BTC | chain |
| 12 Nov 2021 | 0f92016540…5ee5c298 | +0.23 BTC | public ransom-payment tracker |
| 12 Nov 2021 | 0f92016540…5ee5c298 | +0.23 BTC | chain |
| 11 Nov 2021 | a36b21ceab…4afb4539 | +0.1816 BTC | public ransom-payment tracker |
| 11 Nov 2021 | a36b21ceab…4afb4539 | +0.1816 BTC | chain |
| 10 Nov 2021 | dfd823294f…27ebe332 | +0.09 BTC | public ransom-payment tracker |
| 10 Nov 2021 | dfd823294f…27ebe332 | +0.09 BTC | chain |
| 09 Nov 2021 | e3c9e4b776…081f2f12 | +0.115 BTC | public ransom-payment tracker |
| 09 Nov 2021 | e3c9e4b776…081f2f12 | +0.115 BTC | chain |
| 08 Nov 2021 | 4f23121e01…391bad5e | +0.13657056 BTC | public ransom-payment tracker |
| 08 Nov 2021 | 4f23121e01…391bad5e | +0.13657056 BTC | chain |
| 06 Nov 2021 | 72d72c8579…3c25970e | -1.59844711 BTC | chain |
| 01 Nov 2021 | f49b2c97a6…3267b05a | +0.05417055 BTC | public ransom-payment tracker |
| 01 Nov 2021 | f49b2c97a6…3267b05a | +0.05417055 BTC | chain |
Showing 50 of 144, most recent first.
Attributions
- reported as a ransom address of MedusaLocker · verified, high · source statement · recorded by automated process · reviewed
Ransomware families
Groups that operate or use these families
Linked to the family, not to the address. The victims are the ones the group published on its leak site; nothing links any victim to this address.
- medusalocker · operates the family MedusaLocker · corroborated, high · 9 victims of the group, 5 in Brazil
How to read this
- An incoming transaction to an address reported as a ransom address is not a proven payment: only a payment report with evidence allows saying so.
- Whoever sent the money is not labelled: it may be the victim.
- Association is not control: the source links the address to a family or entity, it does not say who controls the wallet.
- Amounts in BTC, as recorded on chain; the price in local currency or dollars varies and is not included.