BankInfoSecurity's latest cryptohack roundup documents two distinct security incidents affecting payment processor Triple-A and the Verus-to-Ethereum cross-chain bridge, the outlet reported in its recurring weekly digest of digital-asset security events.

What does the roundup cover?

The cybersecurity trade publication's roundup series aggregates exploits, fraud cases and enforcement actions across the digital-asset sector. The latest installment, titled "Cryptohack Roundup: Triple-A, Verus-Ethereum Bridge Exploits," flags two incidents that hit infrastructure adjacent to merchant settlement and cross-chain asset transfers.

BankInfoSecurity, based in the U.S., has tracked crypto-related cybercrime since the early industry cycles and maintains a dedicated vertical covering exchange breaches, wallet compromises, smart-contract bugs and bridge exploits.

What is known about the Triple-A incident?

Triple-A operates as a crypto payment gateway that enables merchants to accept digital-asset settlements and convert them into fiat or stablecoin payouts. The roundup's headline confirms Triple-A as one of two named victims in the latest digest. Specific dollar exposure, attacker addresses and vulnerability mechanics fall outside the headline summary.

Payment-gateway compromises carry downstream consequences for merchants who rely on automated settlement flows. Customer-chargeback policies, refund obligations and reconciliation cycles typically depend on the processor's hot-wallet liquidity. An exploit that drains operational reserves can stall payouts, force manual intervention and trigger contractual disclosures to merchant counterparties.

What happened at the Verus-Ethereum bridge?

The second incident named in the roundup targets the bridge connecting Verus, a separate Layer-1 network, to Ethereum. These bridges lock assets on a source chain and mint wrapped equivalents on a destination chain, exposing the contracts to oracle spoofing, signature compromise and validator-key theft.

A successful bridge exploit typically drains liquidity pools rather than individual wallets. That structure concentrates operational impact among liquidity providers and users holding the wrapped asset at the moment of the drain. Recovery paths depend on whether upgrade keys remain in the hands of the operating team and whether the wrapped contract includes pause functionality.

Why are bridges and gateways recurring targets?

Both incident types sit at high-value choke points. Gateways hold merchant float in hot wallets, while bridges secure eight- and nine-figure liquidity pools against smart-contract risk. Attackers consistently prioritize infrastructure that combines large locked value with composable code surfaces.

What's the operational fallout?

For Triple-A, the immediate business question is whether merchant settlement queues resume automatically or require manual treasury intervention. For the Verus-Ethereum bridge, the technical question is whether wrapped-asset holders face redemption delays while the operating team investigates the attack path.

BankInfoSecurity's roundup format surfaces incidents as they emerge across multiple reporting streams, including on-chain analytics firms, project disclosures and law-enforcement bulletins. The publication is positioned to publish follow-up attribution details, exploit postmortems and any recovery actions once the named projects issue formal statements.

The next roundup installment will likely surface additional incidents from the same reporting window, continuing the publication's standing coverage of digital-asset security events across the quarter.