🎉 Exciting news! MetaSleuth has expanded its capabilities to support #SOLANA! 🌟 Discover more about our latest integration: 🔗metasleuth.io/blog/best-sola… Our advanced analytics tools are ready for you to dive into transaction insights. 🕵️‍♂️💼 Don't hesitate and give it a try!

Serial rugpullers launched 16,000+ rugs in the past 3 months They steal millions of $ each week So we built Rug Detector to protect you 👇

My notes for Daniel Von Fange interview on Cyfrin Audits - Best tools for tracing: - Phalcon Explorer app.blocksec.com/explorer/ (by BlockSec) - Tenderly tenderly.co (by Tenderly) - OpenChain openchain.xyz/trace (by samczsun) - Dedaub for contract

ALERT! Our system has detected attack transactions targeting RAMSES's contract on #Arbitrum, resulting in a loss of ~$93K. We have contacted the team, and they have informed us that actions have already been taken. The root cause appears to be an unverified input in

We've just released a detailed analysis of the LI.FI LiFi Attack, where a vulnerability in the GasZipFacet contract resulted in significant losses. 👉 Check out the full report here: metasleuth.io/blog/illicit-f… 📊 Explore the MetaSleuth Chart here: metasleuth.io/result/eth/0x1…

ALERT! Our system has detected a suspicious transaction targeting an unknown project on #Base, resulting in a loss of approximately $1M. The affected project appears to be a #Compound fork, with multiple markets being drained. As the contracts are not open-source, we suspect this

⚠️ 4 days ago, a victim lost around $40,000 in $SOL and $Bonk after signing a phishing signature.💸

looking to run it back very soon with Halborn and other security expert !

📑 Root cause analysis from past DeFi incidents. Hope this stuff can help devs to avoid the same mistakes as much as possible. Now covered 95 incidents. wooded-meter-1d8.notion.site/0e85e02c5ed34d… #DeFi #Web3

🔥🔥

cat is right tho, weighing each potato is crazy

A small hack I use to suppress the "Function state mutability can be restricted to view" warning in my PoCs is a noView modifier to modify state uint _noView; modifier noView() { _noView++; _; }

Actually, I had the same feelings for Solidify dev about five years ago.

Web3 security market is popping - 15 security contests in parallel, so many security researchers booked and busy. Every serious protocol is doing multiple security audits nowadays and I see no slowing down of this trend anytime soon✌️

Y’all please, for the love of all things holy, cement this inside your brains. I have seen SO MANY BLOODY PEOPLE absolutely f*cked recently by this, and it’s a rapidly growing problem.

Inferno Drainer's transferring 319 ETH ($806K) to multiple addresses out fee address collected recently

🧵 [4/9] 🚨 Supply chain attack: A victim likely lost $723K after interacting with a website compromised by the Lottie Player supply chain attack. Remember: Even seemingly legitimate websites may pose risks. Stay vigilant! 🔍 x.com/realScamSniffe…

💡 What leads to restricted access in liquidity pools? 🤔 In our third Critical Spotlight episode, Isabel Burruezo Lopez, Principal Security Engineer at Halborn, explains DoS vulnerabilities in liquidity pools and practical security measures for #blockchain developers. 🛡️

As someone who transitioned from traditional cybersec to Web3 security, here’s how I did it: 1. Learned smart contract development 2. Studied smart contract security basics 3. Practiced in public contests 4. Took on private audits

Let's see what does high/crit in the first 24h means. In 24h protocol can confirm either: Funds drainable Funds permanently lockable Users rekt LP profits/principle gone Traders bleeding on every tx Bots skimming vaults each iteration That's just the first 24h.