On-chain Forensics Brief  ·  Companion to the Aurum / NEYRO brief

The Exit Drain:
how Aurum robbed the wallets on the way out

When the fake trading bot stopped paying, Aurum didn’t just vanish. Under the cover of an “airdrop season 2,” it tricked users into signing a single wallet permission — then used it to drain their crypto straight out of their own wallets. One collector took in millions from thousands of victims, across several blockchains, then bridged the proceeds out to cash out. It is still draining wallets today.

Is the Aurum / NEYRO wallet drainer still active?

Yes. At the time of publication on 28 August 2026 a purpose-built contract was still pulling USDT and USDC out of wallets that had signed a token approval to Aurum or NEYRO under the “airdrop season 2” claim. Signing that prompt moved no money at the time; it granted standing permission to take tokens later.

$2.88M has been taken from 4,411 wallets across BNB Smart Chain, Ethereum, Base and Arbitrum, roughly 98% of it on BNB Smart Chain. That figure is a floor, not a total. The drainer contract hard-codes a single collector address and a single permitted caller, and BSCScan independently labels both wallets “Aurum Foundation 2”.

If you ever connected a wallet to Aurum or NEYRO, revoke your token approvals today. Revoking stops the next withdrawal. It does not return money already taken, and nothing does. No individual is named in this report; identification rests with exchange records under lawful request.

Chains  BSC · Ethereum · Base · Arbitrum Mechanism  Approval-phishing (allowance drainer) Cash-out  Relay bridge → exchange Status  Live — still draining
CrYptOG
Prepared by CrYptOG On-chain Forensic Investigator · Avengers Anti-Fraud Alliance
§

What was examined

The evidence base behind every figure in this report

This audit drew on raw blockchain exports across four networks, the drainer contract’s own on-chain bytecode, and multi-chain flow graphs, spanning 23 July to 27 August 2026. Every figure here was re-derived from that raw material — nothing relies on third-party summaries. The panel below sets out the scale.

4,411
unique victim wallets drained
4,364 41 24
BNB Smart Chain · 4,364 Base · 41 Arbitrum · 24
Segment widths are indicative; exact counts shown in the legend. BNB Smart Chain accounts for ~98% of the drain.
$2.88M
Total drained
a floor — the BSC export capped at 5,000 rows
49
Batch sweeps
transferBatch transactions that pulled every wallet
4,443
Victim pulls
individual token transfers into the collector
4
Blockchains covered
BSC · Ethereum · Base · Arbitrum
10
Operator wallets mapped
collector, owner, funders, consolidation
5
Exchanges & bridges named
Coinbase · HitBTC · Relay · NEAR Intents · Bridgers
~98%
Concentrated on BSC
Base & Arbitrum minor; Ethereum gas-only
1
Direct exchange lead
a Coinbase withdrawal to the operator’s wallet
A What happened

The pivot from Ponzi to outright theft

AURUMThe subject of this report — Aurum Foundation / NEYRO

The first report showed a fake “AI trading bot” that pooled deposits and quietly extracted them. This is what came next. Around 21–23 July, the deposits stopped — and an “airdrop season 2” appeared. To claim it, users were asked to reconnect their wallet, which triggered a MetaMask “increase spending cap” prompt. Approving it doesn’t move money. It hands a stranger’s contract permission to take your tokens later — and that is exactly what happened.

In plain English A token “approval” is like signing a direct-debit mandate. The “airdrop” was bait to get you to sign one. Once signed, the operator’s contract could reach into your wallet and pull your USDT and USDC out whenever it liked — no further confirmation from you. You didn’t send the money; they took it.

$2.88M+
drained in across BSC, Base & Arbitrum — a floor (the BSC export capped at 5,000 rows)
4,411
unique victim wallets across the three chains
~98%
of the drain is on BSC; Base & Arbitrum are small, Ethereum showed only gas
Relay
cash-out routed through the Relay cross-chain bridge — not a direct exchange deposit
B The weapon

A contract built for one job: emptying approved wallets

We pulled the drainer contract’s code from the chain and decoded it. It is small, purpose-built, and self-incriminating. It has no legitimate use.

Drainer contract — decoded from on-chain bytecodetransferBatch executor
// Two hard-coded addresses baked into the contract:
OWNER     = 0x98e7906b5ad64597971a991e20419078b6174e41  // the only caller
COLLECTOR = 0x93d77915179b45b54eb4268be08afe1771928765  // where funds go

function transferBatch(address token, address[] froms, uint256[] amounts) onlyOwner {
    for each victim in froms:
        token.transferFrom(victim, COLLECTOR, amount);   // pull, using the approval
}
function pause() / unpause()  onlyOwner              // operator can switch it on/off
What the code proves Only one address — the operator’s — can run it. It loops through a list of victim wallets and pulls tokens from each using the approval they were tricked into signing. The destination is hard-coded into the contract: every drained dollar was always going to the same wallet. This isn’t a trading tool or a bug. It is a mass-collection machine, and the money’s route was fixed before the first victim ever signed.

C The scale

Thousands of wallets, pulled in batches

On the collector’s own transaction history you can watch it happen: repeated transferBatch calls, each sweeping USDT and USDC out of a fresh set of wallets. Some rows are even flagged “Scam tx” by the wallet-tracking tools themselves.

Wallet tracker showing repeated transferBatch inflows of USDT/USDC into the collector, some rows flagged 'Scam tx'.
The collector wallet’s activity: a stream of transferBatch pulls of USDT and USDC, arriving from a different victim wallet each time — some rows auto-flagged “Scam tx.”
✓ The explorer names it BSCScan independently labels this collector wallet “Aurum Foundation 2” — a third-party entity tag tying the drain directly to the Aurum name, without us having to assert it.

Mapped out, the pattern is unmistakable: a dense swarm of thousands of victim wallets (green, flowing in) collapsing into the single collector node, which then pushes out through a handful of exits (red, on the right).

Arkham visualiser: thousands of green victim-wallet nodes flowing into a central collector, with a small red fan-out to exit points on the Base chain.
Arkham visualiser (Base chain, through 31 July): thousands of victim wallets funnelling into the collector, then a concentrated fan-out to exit points. The same shape repeats on BSC, Ethereum and Arbitrum.
D Where it went

The trail bridges out — and that’s where it gets interesting

Where does the stolen money go? The collector consolidates it and bridges it out through Relay, a cross-chain bridge (its outgoing transfers land on an address BSCScan labels Relay: Depository), alongside a second, unlabelled consolidation wallet 0x47dcff95…94a2a. A bridge moves the funds to another chain and pays them out from its own liquidity — which means the final exchange destination sits on the far side of that bridge, not in a straight line from the collector.

Arkham dashboard for the collector: balance history spiking to ~$2M in late July, and Exchange Usage attributing exchange activity to Binance.
The collector on Arkham: a balance spike to roughly $2M as the drain peaked in late July. Arkham attributes the exchange endpoint to Binance — but that sits beyond the Relay bridge, so it is a strong lead to confirm, not yet a directly-observed deposit.
Victim
signs "increase cap"
Drainer
transferBatch pull
Collector
0x93D7…8765
Bridge out
Relay → (Binance?)
Why this still matters — honestly framed The earlier Ponzi funds vanished into a no-ID exchange by design. This drain instead bridges through Relay, and Arkham points to Binance on the far side — a KYC’d exchange that holds identity, IP and device records. If that endpoint is confirmed by tracing the bridge’s output, it is a realistic route to identifying a human being. That confirmation step — matching the Relay payout on the destination chain to a Binance deposit — is the single most valuable piece of work still outstanding.
E One hand behind it

The gas trail ties it all together

Running a drainer across four chains costs “gas” — small amounts of each chain’s native coin to pay for transactions. All of it came from one distributor wallet, 0x60FE…dd761, which seeded the collector on BSC, Ethereum, Base and Arbitrum on the same day the drain began. That wallet was in turn funded from a single upstream wallet, 0xff72…42aEE.

Arkham profile of the gas-funder wallet 0x60FE…, near-empty, sending small BNB/ETH gas amounts to the collector across chains, itself funded by 0xff72….
The gas-distributor wallet 0x60FE…dd761: near-empty, its only job to push small gas amounts to the collector across every chain — itself first-funded by 0xff72…42aEE.
In plain English A four-chain operation that all gets its running costs from the same wallet, on the same day, isn’t four operations — it’s one, wearing four coats. The gas trail is the thread that ties the chains to a single operator, and it points one step further up to 0xff72…42aEE.

F The operator behind it

One hand on the trigger — and one door to a name

We can map the operator’s own wallet cluster with confidence. It is a small, tight ring of self-controlled wallets, and — unlike the drained money, which bridges away — one of them made a mistake that points at a real-world company.

Proven to be one operator, three independent ways

  • The drainer contract hard-codes the collector as its destination and a single owner address (0x98e7…74e41) as the only address allowed to run it.
  • That owner’s first funding — on the day the drain began — came from the collector itself, across all four chains; the owner later tops the collector’s gas back up. Money flows both ways between them.
  • BSCScan independently labels both wallets under the same name: “Aurum Foundation 2.”

Around this pair sits a handful of small wallets (0x8fc13…, 0x60Df5…, 0x47dcff95…) that pass a few thousand dollars back and forth for fees and housekeeping — all looping within the same ring.

In plain English The operator uses several wallets the way a person uses several bank accounts — shuffling small amounts between them for running costs. We can prove they are all one hand. But the blockchain by itself can never print a name on that hand. For a name, you need a moment where their money touched a real, identity-checked company.

The one door: a Coinbase withdrawal

On 26 July, the operator’s trigger wallet received a withdrawal from a Coinbase hot wallet (USDC, on the Base chain). Coinbase is US-based and among the most strongly identity-verified exchanges in the world — a withdrawal only happens when a verified account holder initiates it. The operator’s internal wallet is not an address advertised to victims, so a Coinbase payout landing on it points to the operator’s own Coinbase account.

Held honestly That Coinbase transfer was only $1. A sum that small could be a test or a self-dust, so we treat it as a strong lead for a lawful request to Coinbase — not as proof of identity. This transaction is confirmed by two independent sources — both BaseScan and Arkham label the sender as Coinbase — so the Coinbase touch itself is not in doubt; only whose account initiated the $1 withdrawal is, and that is answerable solely by Coinbase. A second, weaker exchange touch (HitBTC) appears one hop further out through a funding hub, but HitBTC’s identity checks are lighter. The clean door is Coinbase.
BaseScan transaction page showing: Withdraw 1 USDC to the operator wallet from Coinbase; From address tagged Coinbase 42.
Independent confirmation on BaseScan: the explorer’s own Transaction Action reads “Withdraw 1 USDC to 0x98E7…6174E41 from Coinbase,” and tags the sending address “Coinbase 42” — one of Coinbase’s known withdrawal wallets. Two independent sources (BaseScan and Arkham) agree this is a Coinbase withdrawal to the operator.
✓ What this means for identifying the operator On-chain tracing can map the entire cluster — and it has. But it structurally cannot unmask the human; that step lives with the exchange’s compliance team under lawful request. The value of this section is precise: it tells an investigator or authority exactly which door to knock on — Coinbase — and which wallet to name in the request. No individual is identified here, and none should be, until Coinbase’s records answer that request.
G This is happening now

If you signed the “airdrop” approval, you are still exposed

The collector was still receiving fresh transferBatch pulls within the hour of writing. The approval doesn’t expire — anyone who signed it and still holds tokens in that wallet can be drained again at any moment.

⚠ Do this today If you ever connected a wallet to Aurum or NEYRO — especially for “airdrop season 2” — revoke the approval now. Use a revoke tool (such as revoke.cash) or your block-explorer’s token-approval page, connect your wallet, and cancel any approval to the drainer or to an address you don’t recognise. Do it on every chain you used (BSC, Ethereum, Base, Arbitrum). Move any remaining funds to a fresh wallet. Revoking costs a small gas fee — far less than being drained again.
H Check it yourself

Every address, one click away

Key transaction hashes

I Where we hold the line

What we do — and don’t — claim

Stated limits

  • The $2.88M / 4,411-wallet figure is a floor: the BSC export capped at 5,000 rows, so the true total is higher. The drain is ~98% on BSC; Base and Arbitrum are small and Ethereum showed only gas movement, no stablecoin drain.
  • The cash-out is bridged via Relay. Arkham attributes the eventual exchange endpoint to Binance, but that sits beyond the bridge and is not yet directly confirmed on-chain — it needs the bridge’s far side traced. We flag it as a strong lead, not a proven fact.
  • The drainer owner address is the on-chain operator of the contract. We do not attach any personal name to it. Identifying the human behind it is a matter for exchange records under lawful request, not for public guesswork.
  • A separate community tip links Aurum promoters to earlier collapsed schemes. That is an unverified lead for investigators to corroborate — it is deliberately not treated as fact here, and no individuals are named.
  • Every address in this report is public on-chain data, verifiable at the links above.