Specific exploit primitive not publicly disclosed by TenArmor at time of ingestion. Pattern is consistent with the long-tail of small-cap BSC tokens — common subtypes include: reflection-token transfer math flaws (incorrect application of holder fees), fee-on-transfer accounting bugs that desync pool reserves, owner-privileged mint/blacklist functions abused after key compromise, and LP-pair manipulation where attacker abuses an asymmetric swap to extract reserves. The attack tx should be decoded to determine which subtype applies.
Method: BSC token contract exploit (vector undisclosed). Root cause: Specific exploit primitive not publicly disclosed by TenArmor at time of ingestion. Pattern is consistent with the long-tail of small-cap BSC tokens — common subtypes include: reflection-token transfer math flaws (incorrect application of holder fees), fee-on-transfer accounting bugs that desync pool reserves, owner-privileged mint/blacklist functions abused after key compromise, and LP-pair manipulation where attacker abuses an asymmetric swap to extract reserves. The attack tx should be decoded to determine which subtype applies. Attack tx: 0x2fdd6aef515fb06ce803c55086bb71de712631979809c135cf6d02be133f5cdb. First flagged by TenArmor TenMonitor.
- chain
- bsc
- protocol
- Mail Token
- bug_class
- accounting
- date_occurred
- 2026-05-13
- loss_usd
- $54,600
- source_id
- tenarmor:bsc:0x2fdd6aef515fb06ce803c55086bb71de712631979809c135cf6d02be133f5cdb