We at @ChDefendersEth are proud to announce that we finished at number 5 in the @soon_svm contest. We managed to find a solo high vulnerability. Thank you @cantinaxyz for this opportunity!

Check this project out! Audited by @DefendersAudits btw 🤝

Most audits still stop at the contract. The bug that actually drains you is usually one layer outside it. A signer that got shown the wrong payload. An upgrade that looked fine until storage moved. A helper contract nobody re-read after the last change. We keep finding those at @DefendersAudits. Not because the code is ugly. Because the path around it is. If your review ends when the functions look clean, you’re only half done.

Bitget just lost ~$387M and the interesting line is not the dollar figure. Private keys, they say, were not stolen. Attackers hit the wallet backend, spoofed the transaction data, and let the exchange’s own authorization flow sign the lie. Same week: another bridge drained, another casino wallet emptied. We spent years arguing about key custody. The new failure mode is quieter. The signer is intact. The thing it was shown was not. If your security model ends at “who holds the key,” you are reviewing last year’s incident.

Robinhood Chain just put tokenized NVDA/AAPL, 24/7 markets, and AI agents with wallets on an Arbitrum L2 with a centralized sequencer. H1 2026 security numbers still say half of all losses come from keys, phishing, and ops - not the contracts the auditors actually reviewed. The interesting part isn’t the new chain. It’s what happens when TradFi distribution, RWAs, and agentic trading hit the same attack surface we still haven’t fixed. 🤔

Let’s revive web3sec X! Currently getting into @RobinhoodCrypto and I’m amazed at how bullish the community is! What are some upcoming protocols that might change the game?

Two years passed just like that. Happy to be in this space, alongside @PeterSRWeb3 against all black hats! We are just starting, this was just the tutorial 🤫

There have been so many supply chain attacks recently… Maybe @DefendersAudits we have a solution? 🤫

Time to turn some black hats white again 🎩

I’m not joking when I say that we see deploy scripts using plain text private keys almost every day… I already have a templated finding that I just add to a report once I see such instance. Please please please… protect your private keys and don’t store them in plain text 😬

We are looking for a full-time or part-time Business Developer for @DefendersAudits. The role involves finding potential audit leads and connecting them with the audit team. If you know someone suitable for this position, feel free to contact me here or on TG @ eth0x539. If not, please repost to help spread the word!

Should I start posting some alpha here again? 🤔

Happy new year to everyone! Wish you a more secure year with much less vulnerabilities in live protocols! 🎅

“Security is what matters the most in the end.” - won’t get tired of repeating that!