Shreyas (@SPY8OY) header
Shreyas (@SPY8OY) profile picture

Security Researcher at @CredShields | Bug Bounty Hunter | Audits : Solidity & Rust | Pentester

Web3
Joined December 2020
Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)Photo by Shreyas (@SPY8OY)
Rough math: $6.x b hack, $3b frozen, $1.x b SAFU fund Gap is about $2b, we have $1.x billion in SPCX alone. Remaining gap is (still painful, but) manageable. 🙏
107
👀👀
HUGE: OpenAI just announced they will ship 28 Codex resets over the next 28 days.
125
Great work 🫡
Big news from Immunefi: we just shipped Proof of Duplicate, and it's *the* feature I've been wanting to see for a long time. For years, one of the most frustrating experiences a whitehat could have was submitting a report, putting in the hours of research, the careful write-up, the working PoC… and getting back a one-line "duplicate, closing." No justification and no transparency. No way to push back. That era is over. Starting now, when a submission is closed as a duplicate, it points to the original report. The researcher can read the original. They can compare the reports for themselves... and if they believe the call was wrong, they get a formal dispute button. Verdict upheld means the report stays closed. If the verdict is overturned, the report gets reopened and goes back through triage like nothing happened, including reward eligibility. This matters beyond the feature itself. The whitehat community is the immune system of crypto. Every protocol secured, every exploit prevented, every billion in TVL that didn't get drained. For this immune system to keep working, things have to keep improving for whitehats. Proof of Duplicate is just one piece. There will be more. SR Summer 2026 is coming.
1
303
This was not expected 😭 Code4rena is the place where every security researchers started their journey. C4 will always hold a special place in everyone’s heart 🙌
Replying to @code4rena
After careful consideration, we’ve made the decision to wind down @code4rena. This community has meant a great deal to everyone who has been part of building it, and sharing this news is not easy.
3
166
If you want to deep dive in Anchor accounts you can refer to my repo called Anchor accounts by example. Where I have explained account types and constraints with examples. I hope you guys like it 🤞 github.com/spyboy7711/Anchor…
I am sure that this is the best 4-minute video you need to watch to understand the @solana Account Model youtu.be/fk8TibAJHes?si=u_O9…
4
357
well deserved !
Today, we’re announcing the first allocation from TheDAO Security Fund. We’re supporting @_SEAL_Org and @SEAL_911 - teams that quietly do some of the most important security work in the Ethereum ecosystem. Their impact is significant, and they are among the most closely aligned not-for-profit organizations in the ecosystem. We are donating 69 ETH directly to SEAL and 133.7 ETH to SEAL 911 as well as setting up perpetual @Superfluid_HQ streams.
1
130
Big bounty 🔥🔥
Security researcher ily2 has just earned a staggering $3,000,000 from submitting a critical smart contract bug via Immunefi. That's the largest single payout in web3 security in recent memory. In total, he's submitted 3 reports. All 3 were paid. 100% accuracy. His leaderboard update is coming soon, but you can pledge IMU to him now and earn when he finds the next one: immunefi.com/pledge/ily2
7
586
🚨 Major active supply chain attack just hit npm. Popular package @​ctrl/tinycolor was trojanized — and it didn’t stop there. Over 40 packages were silently modified to steal secrets from dev machines & CI pipelines. Our team at Socket caught it. Full report coming soon. Stay safe out there.
1
245
100% true 🙌
This Post is from an account that no longer exists. Learn more
123
Check this out !
🚨 NEW: VSDeer is live! 🦌 Time to protect your assets by avoiding malicious IDE extensions. VSDeer scans for malicious extensions before you install them. VSDeer runs a nice scam algorithm which detects scammy extensions. Also, you should sandbox all your extensions, so i made sure i wrote you a small guide how. I made sure i gave all the details needed to stay as safe as possible. (link in the next post)
134
👀👀
How to spot misleading audit competition metrics Competitions are crowdsourced audits, where auditors compete to find bugs in a set timeframe. Last year, we acquired @code4rena which does these. We've also seen tons of misleading sales pitches. Here's what to watch out for: 🧵
207
👀👀
The countdown begins... 🪐 Mark your calendars: @ethereumfndn is launching a new $2,000,000 competition on Cantina. We're looking for researchers to help shape Ethereum's future and secure Pectra - the next major upgrade.
1
113
Now you can scan your smart contracts on etherscan using SolidityScan 🚀🚀
Smart contract security made seamless! 🚀 Explore the powerful integration of SolidityScan and @etherscan. View security scores, uncover vulnerabilities, and access detailed reports directly from verified contracts. Safeguard your smart contracts with confidence and ease like never before!
5
141
👀👀👀
Replying to @Rhythmtrader
Keep dreaming. Bitcoin is never going to hit $100,000!
1
158
That’s really great 🙌. I tried opening each contract and searching for specific libraries 🥲
1
164
👀👀👀
Dear @AcrossProtocol team, I’m writing to you during your office hours of 9-5pm on M-F and have no reason to believe today is a national holiday. I’d like to inform you that your token contract has a critical issue. You mistakenly exposed what was meant to be an internal private function written by Open Zeppelin in their ERC20 token implementation, meant for burning tokens, and gave it to your contract owner – allowing you to take tokens out of any wallet at any point in time, arbitrarily rugging any account to 0. Additionally both your @AcrossProtocol and @UMAprotocol contracts have the ability to infinite mint tokens (ironic given @hal2001's rant against infinite mint power on tokens last week), but I’ve already informed you of both of these and you don’t seem to care. To fix the issue without needing to reissue your token: Transfer ownership to a new smart contract that prevents minting beyond the total supply and disallows burning. Since this is a permanent vulnerability, the new contract must be immutable, and it should not include any functionality to transfer ownership. If you have an active bug bounty program feel free to credit this to the @LayerZero_Core team. Best of luck -LZ
1
353
Interesting 👀👀
Zellic is proud to announce Masamune, search for smart contract bugs, reports, bounties, attack vectors, and more. Masamune is a curated index of audit reports, bug fixes, and technical documentation of numerous protocols. Try it here: masamune.app/ Learn more 🧵👇
2
169