🚨SlowMist TI Alert🚨 💸 @slice__so Loss: ~$41k 🔍 Root Cause: FundsModule’s 0x9d2edfac trusted release amounts returned by caller-selected source contracts without verifying that the corresponding ETH or USDC was actually received. In this transaction, two selected contracts returned nonzero amounts while transferring no assets. With flag=true, the function used those unbacked amounts to calculate immediate withdrawals from pooled reserves to the transaction sender. 📌 Attacker: 0xc34572ebb26b9a4c54854aae8d2347108e8c892f 📌 Victim (FundsModule Proxy): 0x61bcd1ed11fc03c958a847a6687b1875f5eacaaf 📌 Vulnerable Implementation: 0x8db3b6f51b594dc87b87a3a3b844de9c0d8d60b5 Powered by #SlowMist.AI Tx: basescan.org/tx/0x02b039a634…

🚨 Recovering Private Keys from 6 Consecutive Observations: Qubic Wallet Vulnerability Analysis During our analysis of @_Qubic_ Wallet, we found that the wallet uses the same non-cryptographically secure Math.random() stream for account seed generation and dejaVu values exposed in network packet headers, potentially enabling private key recovery through network observations. 🔍 Root Cause A shared, non-cryptographically secure random stream → Account seed generation + Network-visible header values ⚠️ Hypothesized Attack Flow 1️⃣ Collect dejaVu values from bridge/peer traffic or the plaintext bridge-to-peer link. 2️⃣ Recover the 128-bit PRNG state using 6 consecutive observations. 3️⃣ Reconstruct the 55-character seed and verify it against the public key exposed in balance requests. 4️⃣ Recover the private key and forge a SchnorrQ signature to transfer assets. Our PoC validated the technical feasibility of this recovery chain. Actual exploitability depends on network trust boundaries, observation continuity, call alignment, and other consumers of Math.random(). 🛡️ Security Recommendations Use cryptographically secure randomness for key generation, conduct comprehensive external security audits before deployment, and review trust boundaries around random number sources and protocol header fields. Read the full analysis ⬇️ slowmist.medium.com/recoveri…

🚨 Threat Intelligence | Analysis of the DarkSword Trojan Backend and iOS Attack Chain Following the public release of #DarkSword-related exploit code in March 2026, DarkSword-PROV2 appeared on GitHub in July, with the attack infrastructure observed operating online in late September. We traced the live attack infrastructure, linked its admin panels to public GitHub repositories, and analyzed the exploit code, payload library, delivery chain, and post-exploitation capabilities. 🔍 Key Findings: 🔹 A complete attack pipeline: The infrastructure integrates exploit delivery, device and data collection, data exfiltration, and crypto wallet fund consolidation. 🔹 Extensive data theft capabilities: The toolkit targets Keychain data, files, messages, and crypto wallet data, with additional capabilities for wallet data decryption and fund consolidation. 🔹 Broader claimed coverage, narrower functional coverage: Although the toolkit claims support for iOS 13 and later, code analysis identifies two functional exploit windows: iOS 18.6–18.7.2 and iOS 26.0–26.1. Many other version entries remain incomplete or unverified. 🔹 Public code weaponized: Publicly available exploit components have been integrated into a deployable attack framework, lowering the barrier to launching sophisticated #iOS attacks. 🛡️ Recommendations Keep iOS updated and avoid untrusted links. Simply opening a malicious page in #Safari may trigger exploitation. If a device has visited a suspicious landing page, treat its seed phrases and private keys as potentially compromised. Use a device that has never accessed the page to create a new wallet and transfer your assets. Also check for abnormal transactions and token approvals across chains, and revoke unnecessary approvals. 🔗 Read the full analysis: slowmist.medium.com/threat-i…

🚨SlowMist TI Alert🚨 💸 Loss: ~$59.8k 🔍 Root Cause: The affected Argent-style smart wallet system exposed two exploitable flaws. In the recovery module, the unrestricted 0x254a2e49 setter allowed a crafted recovery period to make the calculated deadline wrap to a timestamp in the past. This let a recovery backed by a valid guardian signature be finalized in the same transaction, changing the wallet owner. Separately, the execution module failed to reject reuse of an identical signed 0xaacaaf88 payload: it succeeded 19 times in one transaction and nine times in the other. The attacker used the repeated executions to trade around a low-liquidity MARK/WETH pool. 📌 Attacker: 0xc10609ce5c032db92e562e463b1234aab0872b02 📌 Victim: 0xe545b9a69bff1bf0ed2e922551dda4afc8ee8f66; 0x5a79e5772493cf4329682d202aa2d28f85a85440 📌 Vulnerable Contract: 0xf490557d67d934440677a4f16793d5ef319b8ef5; 0x4e50adfc953551286bbd7fee2b2b846d1d227394 Powered by SlowMist.AI Tx: etherscan.io/tx/0xbfed8d3356… etherscan.io/tx/0xa0ee8f9142…

🚨 SlowMist TI Alert 🚨 A fake "Ledger firmware update" campaign is exploiting the recent @Ledger supply chain incident. Looks very real: fake “Genuine check” page, device selection, “Update Now” button. Never click website links to update. Never enter your recovery phrase anywhere. ❌ Stay vigilant! 🔐 #phishing