🚨 Attention all Solidity dev teams - The ultimate Audit Preparation AI tool is here!
Fixing your entire audit preparation process in minutes instead of days for FREE.
Use it before your audit engagement and arrive fully prepared.
Fully open-source. Link in the comments👇
🚨Introducing Web3 Exploit Intelligence:
Free biweekly breakdowns of recent hacks, new vs. recurring attack vectors and what CTOs and devs should check in their own protocols
Learn from others' exploits before they become yours:
cdsecurity.substack.com/p/we…
🚨If you're in Web3, this is the security channel you need:
- major hacks: what happened, how & funds lost
- urgent security alerts
- biweekly reports showing CTOs and devs which vulnerabilities to check in their protocols
don't miss out:
t.me/web3exploitintel
CD Security 🤝 @GrayGooEx
We're partnering with Goo, a DEX and launchpad for tokenized stocks, ETH and robinhood:0x6572eade9fb17f4027baf92feac222b9aa746bd0 on Robinhood Chain.
Serious project who deserve top-tier security with attention to every little detail and as you know that's what we do best.
CD Security 🤝 @SuperteamBlack
Proud to partner with the team backing Solana’s next generation of builders.
Our senior security researchers will help their startups launch securely.
Great projects deserve serious security.
I went through a pile of DeFi papers, articles and courses and kept only the ones worth your time.
30 resources, 10 topics: AMMs, lending, perps, MEV, stables and more.
All linked in the thread below. Bookmark it, you'll want to come back 🧵
🚨 We uncovered a CRITICAL vulnerability that allowed anyone to trigger a token takeover immediately after launch, bypassing a 30-day inactivity restriction.
Here's how it worked:
The protocol had a Community Takeover (CTO) mechanism that was supposed to activate only after a token had been inactive for 30 days.
But there was a critical oversight.
The contract stored the 30-day inactivity period in a uint256 mapping.
However, when checking the restriction, it read the value from a different mapping: uint16.
That mapping was never initialized, so it always returned 0.
As a result, the 30-day protection was completely bypassed.
And it gets worse.
The takeover function had NO access control, meaning anyone could call it directly.
An attacker could:
1. Wait for a new token to launch.
2. Call `enableTokenCto()` immediately.
3. Trigger the takeover and cause the leaderboard ETH pool to be split, with part sent irreversibly to the protocol.
4. Exploit a separate pricing bug to acquire token ownership for just $0.08.
The fix:
Read the inactivity period from the correct uint256 mapping and enforce the intended 30-day restriction.
One wrong storage mapping. Zero waiting period. A CRITICAL security mechanism completely bypassed.
Most devs learn DeFi from random threads and half-finished courses.
So I’m putting together the reading list I wish I’d had:
30 resources across 10 topics.
The DeFi Learning Base drops tomorrow.
Which topic would you open first?
Here's some facts about us:
- we don't have 200 employees
- we have access to some of the best people
- we move ridiculously fast
- the founders are always reachable
- we consistently find valuable shit in audits
- serious protocols keep using us
Exciting partnerships ahead for CD Security!
Love working with teams that take their craft as seriously as we do
The best results come when both sides are willing to go the extra mile 🔥
Auditing only your smart contracts is not enough.
Most of the funds lost in 2026 came from stolen keys, compromised infra, phishing, supply chain attacks, etc.
Audit your contracts. Then audit everything that can move your funds.
We are here to help you with both. 🫡
1st of all: every auditor on our team is a senior with a crazy amount of completed audits behind them.
2nd: we don't assign auditors randomly. We handpick the team based on the protocol. Staking experts audit staking. Lending experts - lending.
Our clients love that 🫡
Want security at the HIGHEST level?
It takes years of hard-earned expertise, deep manual analysis and knowing how to spot what others miss.
Amplified by AI.
That's us. 🫡
🚨HOW THE HELL is @Google ALLOWING THIS? 🤯
the binance devops engineer downloaded a tampered Homebrew installation in order to install an AI coding tool after searching for it on a search engine
homebrew warns about this in their docs: