June 17, 2025
|

AlexLab, LNDFi, MBU: $12M Lost to Access Flaws, Insider Keys, and Decimal Drift

AlexLab’s Clarity contract failed to catch a bad deployment, leading to an $8.4M drain. LNDFi hired a DPRK-linked dev who walked off with $1.3M via backdoored pool logic. MBU’s deposit math applied 18 decimals twice, letting an attacker mint tokens worth $2.2M. Three high-stakes misses, one common theme: no second layer of defense.

In Brief

  • AlexLab lost $8.4M due to an access control vulnerability.
  • LNDFi was exploited for $1.3M after a DPRK-linked developer gained key access.
  • MBU suffered a $2.2M loss from a decimal mishandling in its deposit logic.

Hacks Analysis

AlexLab | Amount Lost: $8.4M

On June 6, the AlexLab exploit on Stacks resulted in a $8.4M loss due an access control vulnerability. The attacker exploited AlexLab’s self-listing feature in the create2() function. The self-listing-helper-v3a contract erroneously approved a malicious token because it failed to invalidate a failed contract deployment. The approval of the malicious token allowed the attacker to drain funds from the liquidity pools. The official AlexLab post mortem claims that the root cause was a limitation in the Clarity smart contract language which fails to verify if a transaction fails.

Press enter or click to view image in full size

Exploited Contract (on Stacks): SP1E0XBN9T4B10E9QMR7XMFJPMA19D77WY3KP2QKC.self-listing-helper-v3a

Transaction: 0xfb4822786771285238e082f46bee1203d9ccb9cedfd1b3e6e574a4908d53474f

LNDFi | Amount Lost: $1.3M

On May 9th, the LNDFi exploit on Sonic resulted in a $1.3M loss due to a compromised deployer wallet. The LNDFi hired an undercover A DPRK-linked developer who gained access to admin keys and initiated unauthorized transactions. The attacker modified smart contracts to bypass pool access controls, allowing any Pool Admin to call restricted functions. Using this backdoor, they drained the pools via the transferUnderlyingTo function.

Press enter or click to view image in full size

Exploited Contract (on Sonic): 0xaa8cc9afe14f3a2b200ca25382e7c87cd883a527

Transaction: 0xd52f317b548bd0f67d32d35404d046e4e60f5af23dac8a502495a8714780bffe

MBU | Amount Lost: $2.2M

On May 11th, the MBU token exploit on BNB Chain resulted in a $2.2M loss. The root cause of the exploit is a vulnerability in the deposit() function that mishandled decimal calculations. By sending 0.001 BNB, the attacker was able to mint MBU tokens 10¹⁸ times larger than it should have. The attacker exploited the 0x371b() (called by deposit()) function which applied the 18-decimal scale twice without correcting it.

Press enter or click to view image in full size
Press enter or click to view image in full size

Exploited Contract (on BNB): 0x637d8ce897bb653cb83ba436cdf76bbe158f05b1

Transaction: 0x2a65254b41b42f39331a0bcc9f893518d6b106e80d9a476b8ca3816325f4a150

What’s a Rich Text element?

The rich text element allows you to create and format headings, paragraphs, blockquotes, images, and video all in one place instead of having to add and format them individually. Just double-click and easily create content.

A rich text element can be used with static or dynamic content. For static content, just drop it into any page and begin editing. For dynamic content, add a rich text field to any collection and then connect a rich text element to that field in the settings panel. Voila!

Headings, paragraphs, blockquotes, figures, images, and figure captions can all be styled after a class is added to the rich text element using the "When inside of" nested selector system.

  1. Follow-up: Conduct a follow-up review to ensure that the remediation steps were effective and that the smart contract is now secure.
  2. Follow-up: Conduct a follow-up review to ensure that the remediation steps were effective and that the smart contract is now secure.

In Brief

  • Remitano suffered a $2.7M loss due to a private key compromise.
  • GAMBL’s recommendation system was exploited.
  • DAppSocial lost $530K due to a logic vulnerability.
  • Rocketswap’s private keys were inadvertently deployed on the server.

Hacks

Hacks Analysis

Huobi  |  Amount Lost: $8M

On September 24th, the Huobi Global exploit on the Ethereum Mainnet resulted in a $8 million loss due to the compromise of private keys. The attacker executed the attack in a single transaction by sending 4,999 ETH to a malicious contract. The attacker then created a second malicious contract and transferred 1,001 ETH to this new contract. Huobi has since confirmed that they have identified the attacker and has extended an offer of a 5% white hat bounty reward if the funds are returned to the exchange.

Exploit Contract: 0x2abc22eb9a09ebbe7b41737ccde147f586efeb6a

Ready to Shift Security Assurance In-House? Talk to Our Security Experts Today.