0x5a26a4875a26…5a26a48a

ConfirmedSecurity632 vB27 sat/vB3 min decode

Blockaid Flags 404,540 USDC Drain From B18TimeBank on Base

Blockaid said an attacker redeemed signed level-reward vouchers before withdrawing 404,540.468304 USDC from B18TimeBank’s settlement contract on Base on Nov. 17, a transfer confirmed by BaseScan.

Blockaid Says B18TimeBank Exploit Drained 404,540 USDC
WitnessBlockaid Says B18TimeBank Exploit Drained 404,540 USDCPexels / pixabay

Outputs

  1. 404,540.468304 USDC moved from B18TimeBank’s settlement contract on Nov. 17.

  2. BaseScan records one transfer at 1:50:59 p.m. ET to the address flagged by Blockaid.

  3. Blockaid said the attacker redeemed signed level-reward vouchers before withdrawing the USDC.

  4. The initial alert did not explain how the attacker obtained usable vouchers.

  5. The exploit occurred on Base, and the root cause remains unresolved.

By Daniel Okafor

An address identified by Blockaid as the attacker withdrew 404,540.468304 USDC from B18TimeBank’s settlement contract on Base on Nov. 17, according to the transaction record on BaseScan.

Blockaid reported an exploit at B18TimeBank after the address redeemed signed level-reward vouchers and then withdrew the funds. In Blockaid’s description, the vouchers were digitally authorized reward claims. Its initial alert did not explain how the attacker obtained usable vouchers, leaving the root cause unresolved.

What did the confirmed transaction show?

BaseScan records a single transfer of 404,540.468304 USDC from the identified settlement contract to the flagged address at 1:50:59 p.m. ET on Nov. 17. The explorer entry independently confirms the amount, the direct source of the funds and the recipient Blockaid labeled as the attacker’s address.

The confirmation covers the withdrawal transfer, not the earlier voucher activity. It therefore corroborates where 404,540.468304 USDC went while leaving the exploit’s opening step unexplained. The available account gives no contract address for the voucher system, code-level explanation or signature detail.

The immediate outflow from B18TimeBank’s settlement contract is measurable at 404,540.468304 USDC. The cited transaction does not establish the final unrecovered loss or the protocol’s full exposure. The source gives no total-loss estimate, affected-user count or recovery status.

No law-enforcement action, regulatory filing, sanctions action or recovery attempt was reported in connection with the Nov. 17 withdrawal. That leaves two separate matters open: the destination and size of the transfer are verifiable on BaseScan, while responsibility for providing the attacker with usable vouchers remains unassigned.

How did Blockaid describe the exploit?

Blockaid said the attacker “redeemed signed level-reward vouchers” before withdrawing $USDC. That sequence places voucher redemption ahead of the settlement transfer. It does not show how many vouchers were used, where the attacker obtained them or whether the claims originated with one participant or several.

The alert’s description of the vouchers as digitally authorized reward claims is the report’s only technical account of the mechanism. No explanation ties voucher possession to the party or process that enabled the attacker to use them. The cited material supplies no code-level, account-level or authorization-flow detail that would support attribution.

For B18TimeBank, that gap matters because remediation depends on identifying which part of the voucher lifecycle allowed unauthorized use. Issuance, authorization, delivery and redemption are distinct control points, but Blockaid’s alert does not say which one was involved. The report identifies the sequence and asset moved, not the defect.

The confirmed withdrawal nevertheless gives on-chain researchers and compliance teams a concrete transfer signature: 404,540.468304 USDC, from the identified settlement contract to the flagged address, at 1:50:59 p.m. ET. The movement is independently verifiable; the route to control of the vouchers remains unproven.

What remains to be established?

A fuller account would need to connect the voucher redemptions to the attacker’s ability to use them and explain what happened between reward issuance and settlement. It would also need to state whether other claims were redeemed and whether the withdrawn USDC can be recovered. The initial alert answers none of those questions.

For counterparties and protocol users, the immediate open question is whether the 404,540.468304 USDC outflow represents the full loss tied to the exploit. The cited report does not quantify additional exposure or describe a response from B18TimeBank.

The next verifiable checkpoint is a root-cause disclosure from Blockaid or B18TimeBank. Until then, the single Base transfer remains the strongest public trace for monitoring the 404,540.468304 USDC outflow, and any resulting change to the protocol’s voucher controls would depend on evidence the initial alert did not provide.

via cryptonews.net (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,514 articles