Bitcoinreported by a source

13AM4VW2dhxYgXeQepoHkHSQuy6NgaEb94

See it on the public explorer ↗

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
20.07453352 BTC
Sent
19.74510304 BTC
Balance
0.32943048 BTC
Transactions
145
First activity
—
Last activity
10 Oct 2024

Checked on 18 Nov 2026 · Source: chain

The source recorded 141 incoming transaction(s), totalling 20.07 BTC, from 12 May 2017 to 27 May 2021. (ransom_payments)

Transactions

The effect is the net change for the address: positive came in, negative went out.

DatetxidEffect on the addressSource
10 Oct 202488fbcc13e7…4159ac1e+0.0005 BTCchain
09 Oct 202412ea399fb5…96f7f6b7+0.0005 BTCchain
27 May 20219ff0abcedf…f507a291+0.0077 BTCchain
27 May 20219ff0abcedf…f507a291+0.0077 BTCpublic ransom-payment tracker
30 Aug 2020ed67062ecc…4ccb69b0+0.001 BTCpublic ransom-payment tracker
30 Aug 2020ed67062ecc…4ccb69b0+0.001 BTCchain
27 Aug 2020f2344f5800…2fd336ab+0.0015 BTCpublic ransom-payment tracker
27 Aug 2020f2344f5800…2fd336ab+0.0015 BTCchain
16 Apr 2020d1b9fd1d2b…f4ef42cc+0.02168194 BTCpublic ransom-payment tracker
16 Apr 2020d1b9fd1d2b…f4ef42cc+0.02168194 BTCchain
22 Apr 2019df24070849…08bfa1f9+0.0584 BTCpublic ransom-payment tracker
22 Apr 2019df24070849…08bfa1f9+0.0584 BTCchain
14 Feb 2018506ef51d77…abc4c1d9+0.06 BTCpublic ransom-payment tracker
14 Feb 2018506ef51d77…abc4c1d9+0.06 BTCchain
07 Jan 20183ef45d1ecb…61da43b0+0.00012 BTCpublic ransom-payment tracker
07 Jan 20183ef45d1ecb…61da43b0+0.00012 BTCchain
03 Jan 2018f02992bd48…162a9855+0.0001 BTCpublic ransom-payment tracker
03 Jan 2018f02992bd48…162a9855+0.0001 BTCchain
03 Jan 2018103ec67385…28d73820+0.0001 BTCpublic ransom-payment tracker
03 Jan 2018103ec67385…28d73820+0.0001 BTCchain
02 Jan 2018bb7b314d05…43607ef8+0.0201 BTCpublic ransom-payment tracker
02 Jan 2018bb7b314d05…43607ef8+0.0201 BTCchain
01 Jan 20186d8660156b…1edfcd74+0.046098 BTCpublic ransom-payment tracker
01 Jan 20186d8660156b…1edfcd74+0.046098 BTCchain
24 Dec 2017568aca49d9…2b908d63+0.02163054 BTCpublic ransom-payment tracker
24 Dec 2017568aca49d9…2b908d63+0.02163054 BTCchain
25 Sep 20173025cb65a9…94266161+0.09 BTCpublic ransom-payment tracker
25 Sep 20173025cb65a9…94266161+0.09 BTCchain
03 Aug 20178def6458a4…4cc293a1-10.06868926 BTCchain
03 Aug 2017a028bb2d4c…9b21cc4c-9.67641378 BTCchain
20 Jun 201729630bec7a…28bf75b9+0.0001 BTCpublic ransom-payment tracker
20 Jun 201729630bec7a…28bf75b9+0.0001 BTCchain
17 Jun 2017a0394353ee…cfa745aa+0.00017093 BTCpublic ransom-payment tracker
17 Jun 2017a0394353ee…cfa745aa+0.00017093 BTCchain
13 Jun 201771aa6667fa…5adce97b+0.00109129 BTCpublic ransom-payment tracker
13 Jun 201771aa6667fa…5adce97b+0.00109129 BTCchain
11 Jun 20172723b37eaa…83bc923e+0.19581815 BTCpublic ransom-payment tracker
11 Jun 20172723b37eaa…83bc923e+0.19581815 BTCchain
02 Jun 2017ea28e28625…b880f94b+0.11947184 BTCpublic ransom-payment tracker
02 Jun 2017ea28e28625…b880f94b+0.11947184 BTCchain
27 May 20179cfdebc6d2…f11d9305+0.13 BTCpublic ransom-payment tracker
27 May 20179cfdebc6d2…f11d9305+0.13 BTCchain
25 May 20176ac937a7cc…446df6eb+0.27 BTCpublic ransom-payment tracker
25 May 20176ac937a7cc…446df6eb+0.27 BTCchain
25 May 201775233255b1…a86be7c3+0.004559 BTCpublic ransom-payment tracker
25 May 201775233255b1…a86be7c3+0.004559 BTCchain
23 May 2017bafebce496…1cf94c05+0.268 BTCpublic ransom-payment tracker
23 May 2017bafebce496…1cf94c05+0.268 BTCchain
23 May 2017560f9b62ce…d0230cf5+0.001 BTCpublic ransom-payment tracker
23 May 2017560f9b62ce…d0230cf5+0.001 BTCchain

Showing 50 of 191, most recent first.

Attributions

Ransomware families

WannaCry

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.

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.