To quote @JeremyClarkson, we did a thing.
🚀 We’re looking for developers to test for the new FYEO Scanner.
If you’re building in Web3, we’d love your feedback. https://t.co/UcK3z8KVxq
The FYEO Security Scanner continuously analyzes your codebase, including pull requests, full repository scans, diff scans, and third-party dependencies, helping you catch potential security issues before they make it into production. It’s built on insights from 300+ real-world security audits and is designed specifically for Web3—not as a generic AI wrapper.
A few things we’re especially proud of:
✅ Continuous PR, full, diff, and dependency scanning
✅ AI trained on real audit experience
✅ Your source code is never stored and is never used to train our models
✅ Runs entirely on FYEO infrastructure—your code isn’t sent to third-party AI providers (FYEO
It’s free to try with a 7-day trial and no credit card required.
We’re actively looking for developers and teams willing to kick the tires, break things, and tell us what you'd like to see. Your feedback will directly shape the product. Full product page here: https://t.co/ubvo9TG1Sn
breaking things is more fun with the best, happy to announce @osec_io & @goFYEO as the Security Partners for SuperteamCTF'26 🔐
50 approved hackers. live leaderboard.
register now → https://t.co/cKAlcBcZ3i
Enrichment Week goes out with a bang 💥
Today, @goFYEO showed our builders how AI is transforming security workflows from threat modeling and repo audits to continuous PR scanning
Huge thanks to FYEO team for an incredible session and for sharing what's next in security tooling
With a 300+ audit/0 post-audit exploit track record, @goFYEO is launching a #AI security scanner to give #Web3 builders constant coverage.
Key features:
- Fine-tune vulnerabilities
- Faster than cloud-based alternatives (~15x)
- Zero token costs.
https://t.co/Dn4sCDyuKR
Over the past several months, we’ve focused on one thing: showing what’s possible when blockchain technology is put to work.
Today, we’re bringing that story together.
Our new brand reflects a simple belief: the future of blockchain will be defined by businesses using the technology to move money, modernize infrastructure, and create entirely new products and experiences.
You’ll also notice a renewed connection to the imagery that inspired our name. Because like an avalanche, transformational change builds slowly, gains momentum, and eventually becomes impossible to ignore.
That’s the moment we believe this industry is entering.
Avalanche. Technology Built for Business.
https://t.co/5zLgvyoEAv
The Aave x KelpDAO rsETH incident is a reminder: exploits aren’t just bugs — they’re failures in threat modeling.
When bridges break, collateral assumptions fail, and liquidity dries up, risk doesn’t stay isolated — it cascades.
Most protocols secure components.
Few model the system.
Threat modeling asks:
→ What if this dependency fails?
→ Where does bad debt flow?
→ How does risk propagate across protocols?
If you’re not modeling:
• Cross-protocol contagion
• Bridge failure modes
• Liquidity shocks
…you’re leaving gaps.
DeFi doesn’t break at the edges.
It breaks at the interfaces.
Breakdown 👇
https://t.co/oSEBeX2siO
The hacks keep coming.
This time: Claude Code.
A dev tool shipped with source maps exposed on npm…
→ making it possible to reconstruct large parts of the codebase
Not a breach.
Not an exploit.
Just a build mistake.
But that’s all it takes.
Attackers don’t need zero-days anymore.
They just wait for you to ship them your internals.
https://t.co/X3ixgn4L5I
Axios just got supply chain’d. Two versions pushed a hidden dependency that installs a cross-platform RAT (macOS, Windows, Linux) during npm install.
No malicious code in Axios itself. Just a poisoned dependency. That’s the point. If you installed: [email protected] or [email protected] then assume compromise. Rotate everything.
This wasn’t sloppy. It was staged, timed, and designed to self-delete. Open source trust is now the attack surface. Read more -> https://t.co/oDRpg4SbMy
@m4rio_eth A threat model is critical and we see so few projects knowing what those are until we show them. If you threat model at the beginning, you can anticipate the edge cases that can lead to devastating incidents. We've been trying to get more web3 projects to adopt this methodology.