Keyword 💙🛠️ (@xKeywordx) header
Keyword 💙🛠️ (@xKeywordx) profile picture

Reviewing smart contracts and making Web3 safer one protocol at a time | SR @NethermindSec

Joined September 2021
Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)Photo by Keyword 💙🛠️ (@xKeywordx)
Keyword 💙🛠️ retweeted
34
239
20
2,524
68,279
Keyword 💙🛠️ retweeted
Introducing the Arbitrum Security Program The Arbitrum Foundation is subsidizing smart contract audits for teams building on the Arbitrum Platform including: > apps on testnet > projects on mainnet > migrating from another chain > dedicated Arbitrum chains Get audited with the likes of @OpenZeppelin, @trailofbits, @cyfrin, @Nethermind and many more Read more below and register today: tally.so/r/3xzEzv?ref=blog.a…
34
49
16
407
39,094
Keyword 💙🛠️ retweeted
There are 6 figure bounties somewhere in your computer You just gotta press the right buttons
8
3
72
2,129
Keyword 💙🛠️ retweeted
Replying to @ProgrammerSmart
"OOS" "Would never happen" "Risk accepted"
3
1
15
755
Keyword 💙🛠️ retweeted
Nonce-Generation Vulnerability in the Zilliqa Ledger App: A critical vulnerability has been identified in the Zilliqa Ledger application affecting the generation of Schnorr signatures for native (non-EVM) Zilliqa transactions. The vulnerability causes signatures to be generated with a predictably weakened ephemeral nonces, from which an attacker can recover the signer’s private key using only publicly available on-chain data. Protective measures are already in place to prevent further loss, and a coordinated remediation plan is being finalised. Users who have signed native Zilliqa transactions with a Ledger device should await official guidance before taking any action. Impact: The vulnerability affects private keys used to sign native Zilliqa transactions with a Ledger device. Any account that has broadcast approximately five or more native transactions signed through the Zilliqa Ledger app should be considered compromised. Its private key can be reconstructed from signatures already recorded on-chain, regardless of any subsequent software update. The issue is confined to the Ledger app’s native signing path. EVM transactions are unaffected. Zilliqa software development kits, including zilliqa-js, gozilliqa-sdk and pyzil, generate nonces correctly and are not affected. Root cause: Zilliqa native transactions are authenticated using EC-Schnorr signatures over secp256k1. Each signature requires a fresh, uniformly random 256-bit ephemeral nonce, (k). The secrecy and full-width randomness of (k) are essential, as any systematic bias can allow the private key to be recovered. The signing routine generated 40 bytes of randomness and reduced them modulo the curve order, correctly producing a uniform 256-bit value. However, when copying this value into the nonce buffer, the code copied the wrong 32 bytes of the 40-byte output. This retained the eight zero-padding bytes introduced by the reduction and discarded eight bytes of entropy. As a result, the most significant 64 bits of every generated nonce were fixed at zero, meaning (k < 2^{192}). A nonce with 64 known bits leaks information about the private key with each signature. With five or more affected signatures, the private key can be recovered in seconds using commodity hardware by solving the resulting Hidden Number Problem through lattice reduction - a well-documented technique for attacking biased-nonce signatures. Because the affected transactions are permanently recorded on-chain, this exposure cannot be reversed by updating the signing application. The affected keys must be retired. Timeline 2019-2026: The defect was present in every released version of the Zilliqa Ledger app across all supported devices. 19 July 2026: On-chain activity consistent with active exploitation was observed. 21 July 2026: The root cause was isolated to the app’s nonce-handling code and confirmed by reproducing the issue against on-chain signatures. Ongoing: A corrected version of the app is being prepared in coordination with Ledger. Release details will be announced separately. Remediation: As soon as the issue was identified, native (non-EVM) transactions were suspended as a protective measure. This has halted further draining of affected accounts while a solution is prepared. Affected accounts cannot be secured through an ordinary transfer. Because their private keys can be derived from data already recorded on-chain, an attacker with access to the same key could attempt to front-run a legitimate transfer as soon as transactions resume. Advising users simply to move their funds would therefore be ineffective and potentially unsafe. A corrected build of the Ledger app has been prepared, restoring full-width nonce generation and preventing further weakened signatures from being produced. However, this does not protect keys that have already been used to sign affected transactions. Those keys must ultimately be retired. A coordinated remediation plan to secure affected balances is being finalised and will be published separately. Until then, users who have signed native Zilliqa transactions with a Ledger device should take no independent action and should rely solely on official Zilliqa channels for instructions. Users who hold or transact with ZIL exclusively through EVM-compatible tooling are not affected. Acknowledgments: @kucoincom played a key role in pinpointing the root cause in the Zilliqa Ledger app nonce generation, recovered affected private keys from publicly available on-chain signatures, and confirmed ongoing exploitation. KuCoin’s timely reporting and responsible collaboration enabled rapid protective measures, helping safeguard users, ecosystem participants, and the broader Zilliqa ecosystem while the remediation plan was being developed. We sincerely appreciate the KuCoin team’s professionalism, technical expertise, and cooperation throughout this process.
As our investigation has progressed, we would like to clarify one important point: At this stage, we have found no evidence that the incident was caused by the exchange’s wallet management or operational processes. We appreciate the exchange’s cooperation in identifying the issue quickly and assisting throughout the investigation. The investigation has instead identified a technical issue affecting transaction signing in a specific set of legacy ZIL1 wallets. We are continuing to verify the precise root cause before publishing a detailed technical report. We will share a full post-mortem, including technical findings and any recommended actions, as soon as the investigation is complete. Thank you for your patience while we work to ensure the information we share is accurate.
46
41
42
194
197,667
Keyword 💙🛠️ retweeted
Dear security researcher From January to June 2026, Immunefi paid out 1,576 bug reports. That is a valid bug found, confirmed, and paid roughly every 3 hours, for six months straight. The bugs are out there. Researchers are finding them every single day and getting paid. And if you're a protocol reading this, understand what that number means. 1,576 exploitable bugs existed in live code this year. The only reason they became payouts instead of headlines is that a whitehat found them first.
7
11
2
103
5,778
Keyword 💙🛠️ retweeted
There are around only 24 hours left to donate to the DAO security fund. I would like to ask you to please donate to Cyfrin Updraft & Tooling. If you know someone who learned security with us, please consider donating! We have been the #1 education platform for onboarding security researchers and developers to Web3 for 3 years straight, 100% for free. qf.giveth.io/project/cyfrin-… Some stats: - Averages 8k students a week - Hundreds of thousands of hours of watchtime in aggregate - Millions of views on YouTube (500k on foundry 1 year ago, 600k 2 years ago, ~200k on intro to security, ~25k on assembly and formal verification, etc) - Thousands of stars on security education on GitHub Not to mention @SoloditOfficial, Aderyn, LocalSafe, WiseSigner, ERC-8213, @CodeHawks first flights & AI first flights (competitive audit live trainings) and more. If you don't like our education, we have a tooling page too: qf.giveth.io/project/cyfrins… Thank you for your consideration!
24
51
7
263
16,366
Keyword 💙🛠️ retweeted
KelpDAO has been hacked 1h ago for ~280 mil
14
14
17
133
25,256
Keyword 💙🛠️ retweeted
Earlier today we identified suspicious cross-chain activity involving rsETH. We have paused rsETH contracts across mainnet and several L2s while we investigate. We are working with @LayerZero_Core, @unichain, our auditors and top security experts on RCA. We will keep you posted as we learn more about this situation. Please follow only the official @KelpDAO handle for the updates.
232
79
160
486
483,067
Keyword 💙🛠️ retweeted
Drift has been hacked. Lots of confusing information going around. I've taken a look at what's actually happening. The core attack sequence is just 3 transactions: 1. Create a new Drift User Account: solscan.io/tx/4xzb1AXSw45Q8S… 2. Deposit 500 Million "CVT" into Drift as collateral: solscan.io/tx/5V72ZK1WejP5Mh… 3. Withdraw Millions of real assets against the provided collateral: solscan.io/tx/2jCAE2SakEHtaZ… (and later transactions) Now, as it turns out, this CVT token was just created a few weeks ago. The core question: How did it become accepted collateral within Drift?
6
23
3
151
33,211
Keyword 💙🛠️ retweeted
still bullish on ai agents for auditing, but there's a long way to go and a lot of work to do. And most of the things we've seen in the past week are just a lot of hype. i think the current wave of agents will converge. they'll all find the same bugs eventually and become glorified static analyzers on steroids. we've seen this movie before. bot races on c4. super cool at first, genuinely useful, but over time they all stopped being unique. one bot dominated market share (shoutout to LightChaser) and the rest died off. meanwhile bugs kept getting found by researchers, hacks kept happening, and the high-paying findings still came from people who sat down and actually digested the codebase. that's where this is headed... NEAR term. let me emphasize that for the people in the back. NEAR TERM. long term, the future is super bright for web3 security, there will be agents that outperform more than 90% of auditors, and they'll be much faster, not only at finding bugs, but also at learning about new bug classes unknown to most. i think all the experiments we're running on auditing agents are an extreme net positive for the space. we're innovating at a rapid pace, every day. i'm hyper bullish that as models keep getting better, the improvements we'll see in ai finding bugs will be exponential. its an exciting and kinda weird time. even still, with all this bullishness for the long term, im still convinced that a dev/auditor with experience and a $20 dollar subscription to some LLM will continue to perform at a high enough level to provide value. its really just a matter of your mentality at this point.
4
1
28
1,325
Keyword 💙🛠️ retweeted
Most people think they can become a smart contract auditor in a few months. They’re wrong. For most people, the entire first year of auditing is beginner mode. You’re absorbing fundamentals, reading real systems, developing focus, learning to reason about code, and building mental models. Between year one and two, you reach junior level (maybe mid if you push hard). This is where you finally contribute, understand larger architectures, catch real issues, and operate inside a team. You’re still early. Expert-level: takes multiple years of real audits and accumulated experience. You don’t become a top auditor in months. It’s a long compounding process of real codebases, real patterns, real audits, mistakes, and continuous learning. Of course there are exceptions. Some people get obsessively focused and progress much faster, but that’s rare.
4
3
75
2,840
Keyword 💙🛠️ retweeted
Can you tell if a ZK circuit is sound, or just correct? Hiring: ZK/Cryptography Auditor Review zkVM guest code + ZK circuits Evaluate soundness, completeness, privacy leakage Skills: Proficiency in Rust + proof systems. Bonus points if you know Noir. jobs.ashbyhq.com/nethermind/…
1
9
1
44
3,467
Keyword 💙🛠️ retweeted
I successfully explained what I do for a living to grandma Grandma loves fruit trees, so I told her: > Imagine you have an apple tree in your garden > Someone might invade and steal your apples > A deer might find it and eat them > Fire blight might attack your tree > If any of these things happen, you instantly lose your apples > So you must protect your tree against these threats > I am the guy who checks whether your protections are good enough > But instead of apple trees, I protect magic money on the internet
9
5
81
2,962
Keyword 💙🛠️ retweeted
AI has collapsed the window between finding a Web3 vulnerability & exploiting it everywhere. One pattern match ➡️ instant ecosystem-wide reconnaissance. Defense response time: nearly zero. Smart Contract Auditor Ravi Kiran on how this changes security nethermind.io/blog/how-ai-is…
2
8
3
26
2,253
Keyword 💙🛠️ retweeted
Replying to @Starknet
@Starknet brothers, Cairo developers now can scan their code for security vulnerabilities using AuditAgent (free tier is generous btw). As far as I know it is the first professional AI-powered security tool for Cairo. Pls tag Cairo developers you know under the post so people will know faster.
AuditAgent now supports Cairo. Scan Cairo contracts on @Starknet. Review findings with predictable results and less noise. Built by Nethermind Security. app.auditagent.nethermind.io
7
5
23
1,552
Keyword 💙🛠️ retweeted
💡AI's Transformative Impact on Web3 Security: Predictions from Late 2026 Onwards💡 From late 2026 onwards what was once a domain dominated by human auditors poring over code will evolve into a hybrid ecosystem where AI amplifies human expertise, reduces costs, and reshapes incentives. 1⃣ Lowering Total Cost of Securing a Protocol One of the most tangible impacts of AI will be a reduction in the overall cost of securing web3 protocols. Today in early 2026 we're already seeing specialist AI agents detecting a broad spectrum of vulnerabilities. Foundational models continue to improve in reasoning and skilled researchers are layering on custom heuristics, creating specialist AIs that can find valuable bugs "at scale". External audits which can easily run into six figures for a comprehensive review have long been a pain point for protocols. If an initial audit uncovers too many findings protocols often face costly re-audits, delaying launches and inflating budgets. By late 2026 specialist "PR Review" agents will be commonly used during development to catch bugs early - and some specialist AI products can catch an impressive range of bugs today; this will only improve by late 2026 & onwards. AI will also supercharge testing methodologies, making it much easier and cost-effective for developers to commonly deliver hardened codebases featuring invariant testing and formal verification. The net effect? Protocols will require fewer external audits, lowering the total cost of securing a protocol. 2⃣ The Evolving Role of Human Auditors Human auditors won't disappear; instead, their work will pivot toward higher-value activities. By late 2026, a growing number of auditors will shift from manual code reviews to developing and refining heuristics for specialist AIs. The trend of auditors consolidating into larger firms will continue; expectations for efficiency will increase across the board. The best auditors will leverage AI to become super-human, highly-efficient bug-finding machines. 3⃣ Capped Auditor Remuneration in Maturing Market The web3 security space is maturing rapidly. In the Wild West days of 2021-2024, sky-high fees and long waiting times were justified by rampant hacks and scarce expertise. But as many skilled auditors transition into creating heuristics for Specialist AI auditors vastly improving their vulnerability detection, clients will increasingly prioritize speed & value. Market share will gravitate toward quality brands that consistently deliver great security output at an efficient price point, who provide great value for money. Intermediate-Senior human auditors will still be able to make a good living but the extremely expensive ones may struggle to remain consistently booked, a trend which played out especially through the first half of 2025 and will accelerate in the future. New & Junior auditors will struggle as the bar to achieving professional success will be raised higher & there will be more competition than ever; they will be completely replaced by Specialist AIs who will consistently perform better providing more value than them. 4⃣ Shorter Exploit Windows and the Elimination of Common Bugs AI's double-edged sword will manifest in exploit dynamics. On the dark side, blackhat AIs will exploit vulnerabilities faster than ever. A protocol launching with bugs in late 2026 could be drained in hours, not days, as blackhat AIs trawl the blockchain in real-time. Conversely, mass adoption of specialist AIs by developers will nearly eliminate certain bug classes. Reentrancy, integer overflows, incorrect rounding direction and access control flaws could become relics, caught routinely during the development process and not even making it to external audits let alone to live deployment. 5⃣ Human-AI Symbiosis Here's the key: Specialist AIs won't stay effective without human input. Auditors and researchers must continually update them with the latest heuristics, drawing from private/competitive audits, post-mortems of hacks and other threat data. This creates a virtuous cycle—humans teach AIs, AIs protect protocols, and the ecosystem grows more resilient providing increasingly efficient security "at scale". In summary, from late 2026 onwards, AI won't replace web3 security professionals but will redefine the field as a collaborative powerhouse. Roles will evolve & markets will mature - for devs, auditors, and protocols: Embrace AI now, or risk being left behind.
13
5
68
4,614
Keyword 💙🛠️ retweeted
Replying to @pashov
1
1
17
738
Keyword 💙🛠️ retweeted
We’re in the final stretch of a security review of @Panoptic_xyz’s upcoming Next Core (V2) codebase. Panoptic is building some of the most ambitious on-chain options infrastructure out there, and it’s been a pleasure working with their team as we wrap up the last pass.
We’re wrapping up our second audit with @NethermindSec as we prepare for another competitive audit with @code4rena. V2 is almost ready, more details coming soon.
3
3
1
16
2,985