←
AMLBot2,270 posts
AMLBot avatar

AMLBot

@AMLBotHQ

Blockchain Intelligence at your fingertips. Crypto Tracing / AML Screening / Incident Response

◷ Joined October 2020▧ 869 Photos and videos
AMLBot avatar
AMLBot@AMLBotHQ·Oct 30

Follow-up on the @binance hack: the part of the stolen funds that is moving is being split fast across hundreds of TRON and EVM wallets. So we are opening Polytrop — a tool we had in the works — as a public beta today. Polytrop follows stolen funds live. From the moment they leave a hacked wallet it labels every attacker address they touch within seconds, and shows how far ahead of the money each label was. Binance case so far (21:20 UTC): • 10 source wallets tracked (TRON + EVM), ~$225M moved out of them • ~1,500 addresses labelled across 7 hops • Median lead 2.5 h — the sender was labelled 2.5 hours before funds left it. • 5 services reached Coverage today: TRON, Ethereum and several EVM chains. Not covered yet: BTC/XRP/SOL. Live case, updating as funds move: polytrop.io/incident/TSpe5HC… It’s a beta. Tell us what you’d want in it — alerts when funds hit a service, a blocklist/API feed, more chains, something else.

Post attachment
AMLBot avatar
AMLBot@AMLBotHQ·Nov 17

Receiving a payment and crediting it are separate steps. Screening belongs between them. Our partner @passimpay screens about 700,000 payments a month with AMLBot. Read our case study: blog.amlbot.com/passimpay-am… We are also giving away 250 AML checks with PassimPay. Details below.

🔍 Where Did Your Customer’s Crypto Come From? One risky crypto transaction could put your entire business balance at risk. Our new article with AMLBot explains how it can happen and what you can do to avoid getting caught off guard. A customer can receive crypto in an ordinary transfer and still know nothing about its earlier history. For a merchant, that means a payment may need additional review even when the buyer has done nothing wrong. 🎁 To go with the article, AMLBot is hosting a giveaway: 5 winners will each receive 50 AML checks, so you can try the screening tool yourself and see how an AML check works in practice. 📍 To participate: • Follow @passimpay and @AMLBotHQ • Like this post • Repost it • Leave a comment We’ll choose 5 winners at random. Winners will need an AMLBot account, and the checks will be credited to the email used for registration. Results: 01.12.2026 🔗 Read the full article via the link in the comments ⬇️

Post attachment
AMLBot avatar
⟳ AMLBot retweeted
AMLBot@AMLBotHQ·Nov 16

Two Lighter accounts linked to @AbraxasCM were drained of ~$15.5M USDC Our tracing shows the proceeds were swapped to ETH, then split into multiple 160 ETH chunks and bridged to Arbitrum. The USDC then landed in Hyperliquid and swapped to XMR1, an XMR variant by @PerpetualCow However, ~3844 ETH ($9M) is still dormant at 0xb3fffca23d4444ee73349825acd84f7b5020e387. We are monitoring the related addresses Related Abraxas Capital addresses on Ethereum: 0x66Cf2f85115CC20bF439720927C1f93De9672068 0x0d1D09312665D31Ed68231b88079a245E0458F6F

Post attachment
ChangeNOW avatar
⟳ AMLBot retweeted
ChangeNOW@ChangeNOW·Nov 13

More than $1.2B in stolen crypto is now subject to court-authorized seizure or restraint measures announced by the US Department of Justice. It's another reminder that responding to major crypto hacks takes more than tracing transactions. Exchanges, blockchain security firms, stablecoin issuers and law enforcement all have a role to play. As Viacheslav Demchuk, CEO and Co-founder of @AMLBotHQ , told us in our analysis of the $6.3B Binance hack: "If $6.3B can walk out of the largest exchange and nobody can do anything about it, no regulator, bank or institutional client will take this industry seriously again." Read our full breakdown of the hack and the industry's response: changenow.io/blog/binance-ha…

AMLBot avatar
AMLBot@AMLBotHQ·Nov 11

Arcus @arcus_xyz was exploited for $2.23M in USDG on Nov 9 The attacker bridged it all out via @RelayProtocol within ~50 minutes. Tracing shows the USDG landed on Ethereum, was swapped into ~475 ETH and ~$1.01M DAI, with another ~$208K routed to Bitcoin through @THORChain and Relay Most of the proceeds still sitting on these three addresses: 0xefbf442599310e5cee1a4edd5c66334c5f30b3dd 0x9a30f6a596f3354ecb90d6bd3a2a16750dcf13d0 bc1qtlme3nlwhlrcdjw5xv8g83t8fakw6snze79wn7 We are actively monitoring this case

Post attachment
AMLBot avatar
AMLBot@AMLBotHQ·Nov 6

Get 100% cashback and an exclusive AMLBot x Kolo card design We’ve partnered with @KoloHub, a crypto wallet with a virtual Visa Platinum card. Use it to pay for AMLBot credits or spend crypto anywhere Apple Pay and Google Pay work. To celebrate, AMLBot users get: • An exclusive AMLBot card design in the Kolo app • 100% cashback on one payment in your first month

0:32

We're excited to announce our partnership with @AMLBotHQ AMLBot is an all-in-one crypto compliance platform: AML wallet screening, real-time transaction monitoring (KYT), KYC/KYB verification and blockchain investigations. One platform, one API and one support team. To celebrate, new AMLBot users get special terms: - 100% cashback on one card payment in the first month - An exclusive AMLBot x Kolo card design in the Kolo app

0:09
AMLBot avatar
AMLBot@AMLBotHQ·Nov 6

The @binance attacker is laundering the XRP leg through @THORChain using scripts/bots Today, 1,027 swaps from 18 wallets sent 51.6M XRP (~$61M) into THORChain, a new swap roughly every 20 seconds for 15 hours. So far 33M XRP has been swapped to ~481 BTC (~$36M), paid out to 27 BTC addresses The bots also glitched: 20 swaps from one wallet carried “NaN” instead of a price. A likely cause is the bot hitting THORChain’s price-quote limit (1 request per second), getting no answer, and sending anyway. THORChain rejected them and returned the XRP Example: xrpscan.com/tx/40E09E0D30A27…

Post attachment

Update: The @binance attacker has now started to move the XRP leg All 233.46M XRP (~$292M) was split from the original wallet into 6 new wallets: five with ~40M XRP (~$50M) each and one with ~33.5M XRP (~$42M). Each received a 1,000 XRP test first The funds have not moved further yet. We are monitoring the related addresses

Post attachment
Allbridge avatar
⟳ AMLBot retweeted
Allbridge@Allbridge_io·Nov 5

Update on the recovery process We want to share an update on the funds related to the July security incident and the ongoing compensation program. A significant portion of the stolen funds has been identified and is currently frozen. These funds are not yet under Allbridge's control, so they cannot be distributed at this stage. We are actively working with law enforcement as part of the recovery process. @AMLBotHQ, which previously supported the KYC/AML verification for the compensation program, is assisting us with the investigation. If and when the frozen funds are successfully recovered, they will be directed toward affected users and the existing compensation program. We want to be careful about timelines. The next steps involve third parties and legal procedures, so the timing is not fully within our control, and we do not want to make promises we cannot guarantee. We are hopeful there will be meaningful progress before the end of the year, but this should not be treated as a guaranteed recovery date. In parallel, the existing compensation program continues to operate, including ongoing ABX buybacks funded by recovered assets and available Allbridge profits. We will keep sharing material updates as the process progresses. Thank you to everyone who has been patient, and to AMLBot for its support with the investigation.

Post attachment
AMLBot avatar
AMLBot@AMLBotHQ·Nov 5

$2.85B of the ~$6.3B stolen in the @binance exploit (~45%) can no longer be moved by the attacker Our investigators dug into the case. USDT and USDC make up 91% of it: $1.77B USDT blacklisted across Ethereum, Tron, Avalanche and Polygon, and $823M USDC. The rest is 21 other assets, including wBETH, XAUt, RLUSD and USD1. Over $2B of the frozen total sits in a single address However, not all of it is an issuer freeze. The @arbitrum Security Council seized 8,426 ETH + 74.56M ARB, @Optimism governance recovered 44.23M OP from the attacker, and 984M BEAM was burned ~77 minutes after the drain began. Binance blacklisted its own wBETH in the attacker's hands

Post attachment

After the @arbitrum Security Council took action, @Optimism has now recovered 44.23M OP (~$4.8M) from the @binance attacker On Oct 31, Optimism's Security Council upgraded the code of the bridge contract linking Ethereum and OP Mainnet. This let them move the attacker's OP without the attacker's approval, sending all 44.23M OP to an address controlled by Optimism. The original code was put back in the same transaction Related transaction: optimistic.etherscan.io/tx/0…

Post attachment
AMLBot avatar
AMLBot@AMLBotHQ·Nov 5

North Korea has denied any role in the $6.4B Binance hack. The FBI attributed the October 29 theft to TraderTraitor. @CoinDesk asked our COO and Head of Investigations Vasily Vidmanov what on-chain data can actually prove: "Onchain analysis can link wallets to one actor. It can't prove nationality or state sponsorship. The evidence supporting the DPRK attribution is cumulative and goes well beyond speculation." Read the full article: coindesk.com/business/2026/1…

AMLBot avatar
AMLBot@AMLBotHQ·Nov 4

After the @arbitrum Security Council took action, @Optimism has now recovered 44.23M OP (~$4.8M) from the @binance attacker On Oct 31, Optimism's Security Council upgraded the code of the bridge contract linking Ethereum and OP Mainnet. This let them move the attacker's OP without the attacker's approval, sending all 44.23M OP to an address controlled by Optimism. The original code was put back in the same transaction Related transaction: optimistic.etherscan.io/tx/0…

Post attachment

Update: The @binance attacker has now started to move the XRP leg All 233.46M XRP (~$292M) was split from the original wallet into 6 new wallets: five with ~40M XRP (~$50M) each and one with ~33.5M XRP (~$42M). Each received a 1,000 XRP test first The funds have not moved further yet. We are monitoring the related addresses

Post attachment
AMLBot avatar
AMLBot@AMLBotHQ·Nov 4

The AMLBot team broke down the @binance hack: the timeline, where the funds are moving, and how Polytrop helps companies spot them. On October 29, between $6.3B and $6.43B left Binance hot wallets, by various estimates. @polytrop, AMLBot’s real-time labelling engine, is now tracking 7.89K wallets linked to these funds. It usually flags a wallet before the funds leave it. Read the full article. There you can also download the CSV address list and request an API key for the case ↓ blog.amlbot.com/binance-hack…

AMLBot avatar
AMLBot@AMLBotHQ·Nov 2

Update: The @binance attacker has now started to move the XRP leg All 233.46M XRP (~$292M) was split from the original wallet into 6 new wallets: five with ~40M XRP (~$50M) each and one with ~33.5M XRP (~$42M). Each received a 1,000 XRP test first The funds have not moved further yet. We are monitoring the related addresses

Post attachment

Update: The @binance attacker has started moving the NEAR leg ~73K NEAR (~$320K) was split from the attacker's main NEAR wallet into 3 new wallets. Two of them swapped ~39K NEAR to BTC and ETH via @near_intents, receiving ~1.63 BTC and ~2.1 ETH. One ~9K NEAR (~$40K) swap appears to have been blocked by @near_intents The third wallet split its funds in two: half was bridged to Ethereum via Omni Bridge and swapped to ETH, the other half was sprayed in small amounts to 71 new NEAR accounts However, 12.3M NEAR (~$54M) is still in the main wallet. We are monitoring the related addresses

Post attachment
AMLBot avatar
AMLBot@AMLBotHQ·Nov 1

Meanwhile, the attacker also moved 485K SOL (~$46M), exactly half of the stolen SOL, to a new wallet: Eze86Ngj2Ue4xKBbTHgXbhm22xnVF4aTxKrhUuVNDrrD The other ~485K SOL remains in the original wallet: AffzFDKZbyMiU11zmVBoAqD25ugpr7xoWWyRyGigBEaU

Post attachment