[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]  void here again Σ [@maximus_void](/creator/twitter/maximus_void) on x XXX followers Created: 2025-07-20 11:31:45 UTC 🚨 What’s Wrong With @Infinit_Labs? (Updated, Fact-Checked 🧠) 🧵For the average CT retardio who needs the full picture👇 1.$49M Hack Was an Inside Job A former dev still had contract access. No multisig. No timelock. He just walked out with $49M. Infinit confirmed this post-mortem. Public Audits (Until It Was Too Late) Before the hack? → No public audits → No bug bounties → No open source repos Now? They’ve hired Halborn & promised to release audit results. Let’s see. Agents = Real Attack Surface Infinit’s agents move your money via natural-language commands. But AI agents are vulnerable to: → Prompt injection → Context poisoning → Bad data sources Recent papers show how attackers can trick them. Box UX (But Getting Better) You type in your intent, it auto-routes. But do you know what bridges/contracts it’s touching? Previews exist now, but chat-first UX still hides complexity. DYOR before signing. 5.Automation = Fast Track to Rugs AI sees a farm with 8000% APY? Might ape in instantly. No pause. No human check. You can’t stop a bad move once it’s signed. 🧠 TL;DR: 💸 $49M insider exploit 🛑 No audits before hack 🧠 Agents exploitable via prompt hacks 👁️ Still not fully transparent ⚡ Fast route to rugville Infinit is bold, but still risky AF. Don’t jump in head first because of UI polish. . XX engagements  **Related Topics** [devs](/topic/devs) [hack](/topic/hack) [$49m](/topic/$49m) [Post Link](https://x.com/maximus_void/status/1946895801403535732)
[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]
void here again Σ @maximus_void on x XXX followers
Created: 2025-07-20 11:31:45 UTC
🚨 What’s Wrong With @Infinit_Labs? (Updated, Fact-Checked 🧠)
🧵For the average CT retardio who needs the full picture👇
1.$49M Hack Was an Inside Job A former dev still had contract access. No multisig. No timelock. He just walked out with $49M. Infinit confirmed this post-mortem.
Public Audits (Until It Was Too Late) Before the hack? → No public audits → No bug bounties → No open source repos
Now? They’ve hired Halborn & promised to release audit results. Let’s see.
Agents = Real Attack Surface Infinit’s agents move your money via natural-language commands. But AI agents are vulnerable to: → Prompt injection → Context poisoning → Bad data sources
Recent papers show how attackers can trick them.
Box UX (But Getting Better) You type in your intent, it auto-routes. But do you know what bridges/contracts it’s touching? Previews exist now, but chat-first UX still hides complexity. DYOR before signing.
5.Automation = Fast Track to Rugs AI sees a farm with 8000% APY? Might ape in instantly. No pause. No human check. You can’t stop a bad move once it’s signed.
🧠 TL;DR: 💸 $49M insider exploit 🛑 No audits before hack 🧠 Agents exploitable via prompt hacks 👁️ Still not fully transparent ⚡ Fast route to rugville
Infinit is bold, but still risky AF. Don’t jump in head first because of UI polish.
.
XX engagements
