Pinned Tweet
This is exactly what I’m seeing with @CapyFi_Protocol right now. 🚩
A “Closed” report doesn’t always mean an “Invalid” bug.
I recently submitted a Critical finding to @CapyFi_Protocol via @Immunefi. The report was escalated then after a day it got closed as "invalid / intentional design", yet the team executed emergency on-chain mitigations within minutes of closing the report. Now, mediation is being blocked. 🛑
Immediately after my report got closed, a controlled address redeemed 5.5 Billion LAC from the caLAC pool—overnight reducing the borrowable reserves by 62%.
To comply with @Immunefi rules and remain professional, I am NOT disclosing any technical details or the vulnerability's nature today. However, when a protocol emergency-mitigates a report while denying the researcher a bounty—and the platform blocks the dispute—it’s a failure for the entire ecosystem. 🛡️🤝
Transparency is the backbone of DeFi.
I Saved Injective's $500M. They Pay Me $50K.
I like hunting bugs on @immunefi . I'm decent at it.
- #1 — Attackathon | Stacks
- #2 — Attackathon | Stacks II
- #1 — Attackathon | XRPL Lending Protocol
- 1 Critical and 1 High from bug bounties (not counting this one)
Life was good. Then I found a Critical vulnerability in @injective .
This vulnerability allowed any user to directly drain any account on the chain. No special permissions needed. Over $500M in on-chain assets were at risk.
I reported it through Immunefi. The next day, a mainnet upgrade to fix the bug went to governance vote. The Injective team clearly understood the severity.
Then — silence. For 3 months. No follow up. No technical discussion. Nothing.
A few days ago, they notified me of their decision: $50K. The maximum payout for a Critical vulnerability in their bug bounty program is $500K. I disputed it. Silence again. No explanation for the reduced payout. No explanation for the 3 month ghost. No conversation at all. To be clear: the $50K has not been paid either.
I've seen others share bad experiences with bug bounty payouts recently. I never thought it would happen to me. I can't force them to do the right thing. But I won't let this be forgotten.
I will dedicate 10% of all my future bug bounty earnings to making sure this story stays visible — until Injective pays what I deserve.
Full Technical Report: github.com/injective-wall-of…
Anyone interested in indexed @traversymedia youtube content.
I built a high-performance search engine to find exactly what you need in seconds.
Check it out here: traversy-cms.vercel.app/?typ…
Features:
⚡️ Full-text search with Postgres GIN indexes
📝 YouTube transcript integration
47
awixor.eth retweeted
Replying to @PatrickAlphaC
@PatrickAlphaC will have a heart attack just because people putting private keys in plaintext 😂
‼️Do not npm install or deploy anything right now
Supply chain attack on axios 1.14.1 - even if you don’t use axios it may be a nested dep.
Pin versions or wait until this is resolved
Replying to @npmjs
@npmjs @GHSecurityLab there is an active supply chain attack on [email protected] which pulls in a malicious package published today - [email protected] - someone took over a maintainer account for Axios
awixor.eth retweeted
this guy literally called this 11 days ago
and this was thariq's response lol
awixor.eth retweeted
"but ser, if you ask your claude/openai/chatgpt/cursor/windsurf/openclaw to ignore sensitive files, it will - use the .cusorignore/rules/llm.md/etc file"
If that is your security posture, you've already lost.
Private keys should never be in plaintext
I just applied to the $4M @BagsHackathon with my project Bags Bracket on @BagsApp
Check it out here 👇
bags.fm/apps/a238fcc2-88df-4…
18
At some point in time in the future, humans will no longer be able to understand code written by AI
5
It's amazing to see people start using my first npm package
npmjs.com/package/git-ward
51
🔥🔥🔥
It’s Next.js Liberation Day.
The #1 request we kept hearing: help us run Next fast and secure, without the lock-in and the costs.
So we did it. We kept the amazing DX of @nextjs, without the bespoke tooling, built on @vite. We’re working with other providers to make deployment a first-class experience everywhere.
Next.js belongs to everyone.
blog.cloudflare.com/vinext/
18
Stop guessing and start structuring your Claude prompts.
claude-craft-kappa.vercel.ap…
1
30
Just merged a PR to the foundry book.
You can now find documentation for MESC support in foundry docs.
github.com/foundry-rs/book/p…
2
2
25

















