🧵+12M in "stuck" crypto might be recoverable.
As long as the deployer nonce on another chain is not burnt and the private key is still around. The recovery mechanism is based on CREATE opcode in the EVM.
Special thanks to @pcaversaccio for help validating this finding.
1/9
Our third-party e-mail provider has been breached. Please be aware that the email named ‘Critical Security Alert: STM32 Entropy Vulnerability’ is not coming from us, and it’s a phishing attempt. Do not click on any link.
We have taken down the domain, and we are investigating the situation, including how the hackers got access to our legit domain.
We are proud to onboard @namidefi as our new client and announce our Security Partnership with them.
A truly dedicated team which has big aims and is very hungry to achieve those.
We look forward to supporting their growth with trusted, high quality security expertise.
meet OmniSwap, the first of many products in the Nami family
- 15+ providers compared
- quotes verified through onchain simulations and ranked by REAL output
- multiple swaps in a single transaction with the Batcher Engine
- isolated approvals acting as shield for your wallet
-audited by Bailsec
Welcome to Nami, a unified on-chain system where trading, liquidity, voting, and credit operate across chains as one coordinated protocol.
One Engine.
Multiple Products.
One connected DeFi experience.
Welcome to Nami, a unified on-chain system where trading, liquidity, voting, and credit operate across chains as one coordinated protocol.
One Engine.
Multiple Products.
One connected DeFi experience.
everyone check your rust codebases!!! short prompt
Check <repo> and this machine for the Aug 2026 crates .io compromise:
arrayref 0.3.10, append-only-vec 0.1.9, proc-macro1, proc-macro-en.
Grep every Cargo.lock/toml, then check ~/.cargo/registry for those crates, /tmp/rust-setup, egress to 23.254.165.112, and new LaunchAgents
since 2026-08-19. Report only, don't fix.
SC-AI assessment by @bailsecurity has been incredible. ahead of our main audit it spotted serious issues, and the act of resolving them made us reflect on and revise key design decisions and simplify modules that could have otherwise been problematic. By far it's the best AI auditing tool out there I have experienced so far thanks to the extent and depth it can analyze that a manual review might miss. We ran it over multiple rounds, roughly a day per module and it kept surfacing findings worth fixing. Running it recursively is what really paid off, audit a module, fix it, run it again, with fewer findings each pass until they came back clean. I believe it's a must-have as a preflight assessment before any serious audit engagement.
Some of our partners ran their codebases through every major AI auditing tool available.
Then they tried ours.
The delta was... uncomfortable.
All our partners and us will share the results very soon.