KiloEx, Nitron, and Alkimiya Lose $8.4M: No Checks, No Controls, No Excuses
KiloEx gave away $7.4M by omitting access controls in price setting. Nitron lost $951K to a vault donation trick that fooled their oracle. Alkimiya failed to validate a typecast, letting an attacker overflow a mint and extract $96K. All preventable.
In Brief
Nitron suffered a $951K price manipulation attack.
KiloEx was exploited for $7.4M after missing access controls.
Alkimiya lost $96K due to an unsafe integer conversion.
Hacks Analysis
Nitron | Amount Lost: $951K
On May 16, the Nitron (on Demex) exploit on the Arbitrum chain resulted in a $951K loss due to a price manipulation attack. The attacker donated fsGLP tokens to a low-TVL dGLP vault, significantly increasing the supply and artificially inflating the token price. Nitron’s oracle used this inflated rate to calculate the value of dGLP. The attacker then used the overpriced dGLP as collateral to borrow other assets and make a profit. Nitron confirmed that they will introduce stricter withdrawal protections and on-chain TVL-based circuit breakers.
Press enter or click to view image in full size
Exploited Contract (on Arbitrum): 0xab19bdaeb37242fa0f30486195f45b9cf5361b78
On April 14, the KiloEx exploit on the Base chain resulted in a $7.4M loss. The root cause of the exploit was missing access control in the setPrices() function in the KiloPriceFeed contract. The setPrices() function allowed unauthorized calls to increase or decrease the token price. By submitting a forged signature, the attacker manipulated ETH prices, initially setting it to $100, then opening a leveraged long position. Later the attacker set the price to $10,000, closed the long position and made a profit.
Press enter or click to view image in full size
Exploited Contract (on Base): 0x22c40b883b5976f13c78ee45ead6b0cdc192dae5
On March 28, the Alkimiya exploit on the Ethereum mainnet resulted in a $96K loss. The root cause of the exploit was that the private collateralizedMint() function did not validate the integer size when converting from uint256 to uint128. The attacker used a flash loan to call collateralizedMint() with a request for 2¹²⁸ + 1 shares. The function converted this value to a 128-bit integer without bounds checking and reduced the value to 1 share. The attacker then transferred out 2¹²⁸ — 1 shares, leaving 2 shares in the contract. When the attacker redeemed the balance, the contract miscalculated and returned more WBTC than expected.
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.
Follow-up: Conduct a follow-up review to ensure that the remediation steps were effective and that the smart contract is now secure.
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.
