November 3, 2025
|

Typus, Seedify, UXLink: $16.4M Lost to Missing Checks, Key Leaks, and Mint Abuse

No auth check. No key hygiene. No mint controls. Three protocols got wrecked by three of the oldest failure modes in DeFi. Typus let anyone write to its oracle. Seedify leaked its remote config keys. UXLink handed out mint rights like coupons. This isn’t about complexity. It’s about discipline.

In Brief

  • Typus Finance lost $3.4M because update_v2() lacked authorization checks.
  • Seedify lost $1.7M after a private key compromise.
  • UXLink lost $11.3M due to unauthorized minting.

Hacks Analysis

Typus Finance | Amount Lost: $3.4M

On October 15th, the Typus Finance exploit on the Sui blockchain resulted in a $3.44M loss. The root cause of the exploit was a missing authorization check in the oracle contract’s update_v2() function. This allowed unauthorized addresses to manipulate oracle price feeds without validation. The attacker updated oracle prices to artificially inflate asset values within the TLP contract. By manipulating these prices, they drained 588K SUI, 1.6M USDC, 0.6 xBTC, and 32K suiETH from the liquidity pool.

Exploited Contract (on Sui): 0xaf44818c67a878b9eba0c63186b00e80d9fc3d1e2ae02f00fa3993b0e683bff3

Transaction: 6KJvWtmrZDi5MxUPkJfDNZTLf2DFGKhQA2WuVAdSRUgH

Seedify | Amount Lost: $1.7M

On September 13th, the Seedify exploit across multiple chains resulted in a $1.7M loss due to a private key compromise. The attacker gained unauthorized control of the SFUND_OFTv1 contract and called the setTrustedRemoteAddress() function to configure a malicious contract as the trusted remote address. This allowed the attacker to mint SFUND tokens and make a profit.

Press enter or click to view image in full size

Exploited Contract (on Base): 0x633E254585aDE6E9d40d2A4B8CC2F3769B94cb48

Transaction: 0x1dd7c101c18cd1adc80c4c68ce480862245a7223f8e5182136aed316eae54ac9

UXLink | Amount Lost: $11.3M

On September 23rd, the UXLink exploit on the Arbitrum chain resulted in an $11.3M loss due to unauthorized token minting. The root cause of the exploit was that the attacker gained access to minting privileges and created new UXLINK tokens outside the protocol’s whitepaper specifications. According to the UXLink team, major centralized exchanges froze the majority of the hacker’s assets and limited the damage.

Press enter or click to view image in full size

Transaction: 0x35edac40767f65d4d1382f0f55cda2f4db321313e16fe059079f0113f9cb5696

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.