Must favorite feature : Signal 👀
This one help you to find correct target, imo
Immunefi Studio opens November 18, the same day the @base audit competition begins.
Here's what you get:
✦ Signals: see how programs respond, pay, and how crowded they are
✦ Instascope and Blueprint: see the scope as code and a map of the protocol
✦ Alerts: get notified when scope or code changes
✦ Workspace: manage your cases and tasks in one place
✦ Studio Review: get feedback on your report in about 3 minutes. Get a green verdict and submit directly to the program with no fee and no accuracy penalty if the report is closed
✦ Audit competitions: everything set up for you from day one, starting with @base
✦ Studio MCP: give your AI agents access to all of it
And we've already seen what Studio can do.
During the beta, researchers who checked most of their reports with Studio Review had:
✦ 2.5x higher valid report rates
✦ 63% fewer reports closed as duplicates
But Studio isn't just about writing better reports. It's also about knowing where to hunt.
"It really help me a looooot to choose the next target very wisely, its really useful and help me really good to know where to put my focus and time on." — @ZeroK_____
So, how do you get access?
Studio is invite-only. Access will grow through researchers inviting researchers they trust, starting with our Ambassadors.
Already on the waitlist?
Some of you got early access and helped us build Studio. But demand was much higher than we could handle during beta.
Now we're opening the doors to more researchers.
Want access?
Comment "." below.
Our Ambassadors will look at the comments first when invites open on November 18.
1
131
Nantikan kota kota selanjutnya 😂
small gathering of security-minded individuals who have already helped secure numerous Web3 protocols but choose to keep a low profile because, well, you know why 😂
thanks sudah datang ges @0xdemonnn @0wlxzy @0xVrka @BimaJadiva07 @/om eric dan tentunya solo ponder om @xfajarr
2
7
288
My favourite feature is Signal , so good!
AI made it easier to submit reports. More reports meant more noise, which meant more restrictions: submission fees, rate limits, and accuracy penalties.
Immunefi Studio helps you avoid wasting time and money.
Signals helps you choose where to hunt. Review checks your report before you submit, so you can send stronger reports.
And the credits you earn from valid work can pay for your Reviews.
But don't take our word for it:
"my first 5-fig report ($50k) came from picking the program through /signals, the data showed exactly where to look/priority. and /reviews changed how I work entirely, went from submitting more submissions to stacking 3 criticals back to back because I started focusing on quality over quantity." - @Horvix_
Studio launches soon.
I just found a confirmed bug on @immunefi #immunefitribe immunefi.com/s/ss/?severity=…
Another one 🍻
5
34
806
Of course this is not available for independent researchers, only for 'selective partners'. What's the point of a daybreak then?
According to my personal experience daybreak blue is no better than Opus 5.5 @AnthropicAI
Simply unsubscribe @ChatGPT @OpenAI
Introducing GPT‑6 Cyber: a major advance in security research that pairs stronger capabilities with better model alignment.
The model powered the Linux kernel research we announced yesterday, and security teams at companies like Mozilla, Palo Alto Networks, Calif, and Cisco—alongside our own at OpenAI—are already putting it to work.
GPT-6 Cyber is available to select Daybreak Red customers and we are expanding access over time.
openai.com/index/introducing…
2
175
The Arbitrum Security Council has taken emergency action to rescue the 74,559,805 ARB and 8,425 ETH being held in the address on Arbitrum One that is identified as connected to the Binance exploit. The Security Council acted by weighing its commitment to the security and integrity of the Arbitrum community and Arbitrum governance without impacting any Arbitrum users or applications.
After significant technical diligence and deliberation, the Security Council identified and executed a technical approach to move funds to safety without affecting any other chain state or other Arbitrum users.
As of October 30, 2026 time, the funds have been successfully transferred to an intermediary frozen wallet. They are no longer accessible to the address that originally held the funds, and can only be moved by further action of the Security Council or a vote of Arbitrum DAO governance, which will be coordinated with relevant parties.
Feeling blessed and grateful 🙏
Submitted 5 bug bounty reports: 1 Critical, 2 High, and 2 Medium. All findings were confirmed and fixed by the project team.
Thank you to the team for taking security seriously and recognizing my work. Proud to help make the ecosystem safer!
10
86
2,334
0xDemøn retweeted
OpenZeppelin is now officially a part of S&P Global.
The acquisition we announced in September is finalized. OpenZeppelin’s decade of securing and building the infrastructure onchain finance runs on now meets @SPGlobal's more than a century of helping markets understand risk. Together, we can help institutions and builders move onchain with greater confidence.
To our clients and to all the users of OpenZeppelin open source tools:
• OpenZeppelin Contracts and all our open source applications and tools remain open source, free and publicly maintained on GitHub.
• Security audits, secure development work and ecosystem programs continue with the same team, brand, quality and customer experience, now backed by S&P Global’s research capacity, market data and institutional reach.
For the last decade, OpenZeppelin has set the security standard for onchain finance. Now we take it to the scale of global finance.
Read the full announcement: press.spglobal.com/2026-10-2…
Full write-up & technical breakdown is live on Medium.
Diving deep into the CosmWasm / IBC v2 bugs, git fix correlations, and the administrative handling:
medium.com/@hdny679/triaged-…
The engineers behind @cosmos CosmWasm wasmd are clearly capable of telling real bugs from spam.
I reported 3 vulnerabilities through @Hacker0x01, and the Cosmos team validated and officially triaged all of them.
They had the capability to handle this properly. Instead, there was no follow-up, no technical discussion, and zero professional handling. it turned into a free security audit handled in bad faith: using retroactive rules to slap a spam label on valid findings right before quietly pushing the exact same patches, then locking every single report.
Code and commit trails don't lie, @cosmoslabs_io labels do.
I broke down the technical root causes, logic flaws, commit trails, and evidence in the write up: github.com/7tecra7/cosmos-sp…
The engineers behind @cosmos CosmWasm wasmd are clearly capable of telling real bugs from spam.
I reported 3 vulnerabilities through @Hacker0x01, and the Cosmos team validated and officially triaged all of them.
They had the capability to handle this properly. Instead, there was no follow-up, no technical discussion, and zero professional handling. it turned into a free security audit handled in bad faith: using retroactive rules to slap a spam label on valid findings right before quietly pushing the exact same patches, then locking every single report.
Code and commit trails don't lie, @cosmoslabs_io labels do.
I broke down the technical root causes, logic flaws, commit trails, and evidence in the write up: github.com/7tecra7/cosmos-sp…
0xDemøn retweeted
Update: Immunefi upheld the duplicate closure.
Their own fix-bypass policy says a bug that wasn't effectively fixed should be reported.
That's exactly what I did. The PoC in my report still works after the attempted fix.
Yet their mediation response didn't even mention the fix-bypass policy.
So what's the point of having it?
Why would any whitehat spend time checking whether a fix actually works if the answer is still "duplicate, no reward"?
I thought Immunefi was supposed to keep this fair.
Instead, they're keeping their clients happy.
Projects trying to rug whitehats seem to be the norm lately.
I recently found a High severity bug. The project closed it as a duplicate of an earlier report. Which is technically true since both have the same root cause.
The funny part is they already tried to fix it.
And failed.
My PoC demonstrates that their fix can be bypassed and the bug is still exploitable.
@immunefi even has an explicit fix-bypass policy for cases like this:
immunefisupport.zendesk.com/…
But I guess it's easier to close the report than fix the bug and pay the whitehat.
0xDemøn retweeted
I decided to give Immunefi Studio Review a shot before submitting a High severity finding.
The submission for this particular program costs $75 so I decided to pay $20 for a Studio review first to sanity-check the report.
Immunefi Studio came back with "Ready" - "meets standard escalation criteria with no blocking technical flaws".
To be fair, it suggested a couple of improvements to the PoC which I applied to the report before submitting.
So I paid the $75 and submitted.
15 minutes later, my favorite guy Andrew closed it as a duplicate of a report submitted 9 days earlier.
So that's $20 for Studio Review + $75 submission fee = $95 to have one Immunefi bot tell me "send it" and another Immunefi bot tell me "duplicate report".
That's the part I'm struggling with.
Immunefi Studio is explicitly advertised as checking duplicate risk too.
If a duplicate has already been sitting in your system for 9 days and the Review bot can't catch it, but the triage bot catches it almost immediately after submission, then what exactly is the value proposition here?
@immunefi / @MitchellAmador - I genuinely think this is useful feedback if you're still iterating on Immunefi Studio.
But from the whitehat side, this flow feels pretty broken.
Especially when it costs $95 to get to this outcome.
0xDemøn retweeted
Small @immunefi ask:
When a report is closed as "Duplicate of invalid", show why the original was rejected as invalid.
Right now we only see the original report, NOT the closure reason.
It feels like basic courtesy when I paid 75 USDC to submit.
.@DarioAmodei and @sama!
it is high time you put some money into KYC, or whatever trust/verification system you want, and give legitimate security researchers access to your best models.
1. we’ve helped secure both of your companies multiple times against issues that could have had serious consequences. i wouldn’t be surprised if we can keep doing that, and i also wouldn’t assume every capable attacker is reporting what they find.
2. there is now a KVM escape that, if researchers hadn’t found it first, could have been exactly the kind of thing your models eventually find in another hugging face style incident.
you know, the list will keep growing, this is not the end.
it rationally makes sense to get as many trusted researchers and companies as possible red teaming your companies, your models, and the infrastructure they depend on.





















