18wRbb94CjyTGkUp32ZM7krCYCB9MXUq42
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
- 21.80946218 BTC
- Sent
- 21.80945671 BTC
- Balance
- 0.00000547 BTC
- Transactions
- 104
- First activity
- —
- Last activity
- 06 Oct 2020
Checked on 18 Nov 2026 · Source: chain
The source recorded 57 incoming transaction(s), totalling 21.81 BTC, from 01 Jul 2019 to 04 Oct 2020. (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 |
|---|---|---|---|
| 06 Oct 2020 | a77f61fcb0…f79a0e90 | -0.09333341 BTC | chain |
| 04 Oct 2020 | 2f23f01fb5…f8f5cc8f | +0.09333341 BTC | public ransom-payment tracker |
| 04 Oct 2020 | 2f23f01fb5…f8f5cc8f | +0.09333341 BTC | chain |
| 02 Oct 2020 | 1f838499a1…60eac57c | -0.09152318 BTC | chain |
| 02 Oct 2020 | 92077c646e…99d51430 | +0.09152318 BTC | public ransom-payment tracker |
| 02 Oct 2020 | 92077c646e…99d51430 | +0.09152318 BTC | chain |
| 14 Sep 2020 | 14322d8fac…993f7f67 | -0.11583402 BTC | chain |
| 10 Sep 2020 | 4b25bbd903…dc3fb999 | +0.11583402 BTC | public ransom-payment tracker |
| 10 Sep 2020 | 4b25bbd903…dc3fb999 | +0.11583402 BTC | chain |
| 26 Aug 2020 | e5a4dece49…8da4e046 | -1 BTC | chain |
| 25 Aug 2020 | 893ae3b870…ee3f77c3 | +1 BTC | public ransom-payment tracker |
| 25 Aug 2020 | 893ae3b870…ee3f77c3 | +1 BTC | chain |
| 12 Aug 2020 | d1922bb321…e3e080c0 | -0.04257975 BTC | chain |
| 06 Aug 2020 | bc6730a7c1…2d20ffaf | +0.00000547 BTC | public ransom-payment tracker |
| 06 Aug 2020 | bc6730a7c1…2d20ffaf | +0.00000547 BTC | chain |
| 06 Aug 2020 | 4835e7f903…5a202d33 | +0.04257975 BTC | public ransom-payment tracker |
| 06 Aug 2020 | 4835e7f903…5a202d33 | +0.04257975 BTC | chain |
| 01 Aug 2020 | d24a90bd15…fd4d5112 | -0.04499 BTC | chain |
| 29 Jul 2020 | 5247f634de…24e4e06f | +0.04499 BTC | public ransom-payment tracker |
| 29 Jul 2020 | 5247f634de…24e4e06f | +0.04499 BTC | chain |
| 17 Jul 2020 | c8ce38b503…3384116e | -0.8 BTC | chain |
| 13 Jul 2020 | bb112589b1…348c5b92 | +0.8 BTC | public ransom-payment tracker |
| 13 Jul 2020 | bb112589b1…348c5b92 | +0.8 BTC | chain |
| 04 Jul 2020 | fb09a31e3c…574731b2 | -0.5 BTC | chain |
| 02 Jul 2020 | 6069106289…50f3f1dd | +0.5 BTC | public ransom-payment tracker |
| 02 Jul 2020 | 6069106289…50f3f1dd | +0.5 BTC | chain |
| 25 May 2020 | 2391f27d9b…ed451132 | -0.14606148 BTC | chain |
| 22 May 2020 | 22ce9c18a3…aacefbcd | +0.14606148 BTC | public ransom-payment tracker |
| 22 May 2020 | 22ce9c18a3…aacefbcd | +0.14606148 BTC | chain |
| 21 May 2020 | 92b3999d5b…4a6f21e7 | -3.722 BTC | chain |
| 21 May 2020 | 25140e129a…a4ffd9cb | +3.722 BTC | public ransom-payment tracker |
| 21 May 2020 | 25140e129a…a4ffd9cb | +3.722 BTC | chain |
| 03 May 2020 | f78779d878…cfbb24dc | -0.1009589 BTC | chain |
| 26 Apr 2020 | 0a98ac8c80…426bcffa | +0.1009589 BTC | public ransom-payment tracker |
| 26 Apr 2020 | 0a98ac8c80…426bcffa | +0.1009589 BTC | chain |
| 26 Apr 2020 | ef9f47dae0…90bcdf0b | -0.30096027 BTC | chain |
| 22 Apr 2020 | 4e946b519c…4b8b2243 | +0.30096027 BTC | public ransom-payment tracker |
| 22 Apr 2020 | 4e946b519c…4b8b2243 | +0.30096027 BTC | chain |
| 27 Mar 2020 | df0d810942…89391d3e | -0.22313 BTC | chain |
| 26 Mar 2020 | 26218884ca…e1819c33 | +0.22313 BTC | public ransom-payment tracker |
| 26 Mar 2020 | 26218884ca…e1819c33 | +0.22313 BTC | chain |
| 25 Mar 2020 | bcabcd67dc…07cf78eb | -1.12791506 BTC | chain |
| 25 Mar 2020 | 37050719fd…d6e21a73 | +1.12791506 BTC | public ransom-payment tracker |
| 25 Mar 2020 | 37050719fd…d6e21a73 | +1.12791506 BTC | chain |
| 20 Mar 2020 | 503f5a4d15…0386e704 | -0.73737986 BTC | chain |
| 19 Mar 2020 | d6685f2ed1…457728a7 | +0.73737986 BTC | public ransom-payment tracker |
| 19 Mar 2020 | d6685f2ed1…457728a7 | +0.73737986 BTC | chain |
| 17 Mar 2020 | 607bf2e12e…a862a45d | -0.12254737 BTC | chain |
| 13 Mar 2020 | 68a3c883c9…a388ae77 | +0.12254737 BTC | public ransom-payment tracker |
| 13 Mar 2020 | 68a3c883c9…a388ae77 | +0.12254737 BTC | chain |
Showing 50 of 107, 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.