RustyRabbit

non fungible dad
security researcher

[RustyRabbit @_RustyRabbit]

@ge6a_bg Or the top SRs missed one obvious bug and they're all duplicates.
Incentives are screwed up. At this point it's probably better to not submit anything. Wait to see if anyone else caught it in a contest and submit it in the bug bounty if they didn't.

[Bug Bounty @bounty50657]

@ge6a_bg People do not trace back the bugs and validate them, people do no use false claim filter for maybe third run to validate bugs, they just submit what the Ai report to them.

[Kiru survival arc @0xKiruse]

@banteg >it's too powerful to release!
>5 supply chain attacks
>3 exploits on linux
>5 exploits on windows
>github compromised
>all within 2 months
brothers idgaf if it's "too powerful" obv the other side is ahead of the race already 😭

[RustyRabbit @_RustyRabbit]

@MemoryReboot_ A more apt analogy is the Mac is a Mercedes van on the Nordschleife and the GPU based system is a hot hatch running on the same track. The hot hatch is faster but it isn't carrying the same load.

[RustyRabbit @_RustyRabbit]

@hrkrshnn What is needed is policy driven de Sion. Biggest problem is probably how do you express the rules when the actions are by nature ambiguous and situational.

[LonelySloth @lonelysloth_sec]

You think there's been lots of hacks?

There are companies right now replacing software that was working perfectly well for years, that we can inspect and find bugs in...

with "agents" we can't inspect, commanded by prompts that influence its output in ways we can't map, and that are mathematically incapable of separating instructions from untrusted data.

All of that for 1,000,000,000x the compute cost, and an error rate orders of magnitude worse than before.

Since businesses now apparently exist to be AI customers and justify AI valuations instead of providing products and making profits, you can expect the trend to keep going for a while.

[RustyRabbit @_RustyRabbit]

@PatrickAlphaC I keep asking myself "what the hell is DPRK doing better than we are, and what can we do or how can we organize ourselves to beat them".
Still haven't found what I'm looking for.

[banteg @banteg]

layerzero attack was not rpc poisoning

in networking poisoning is when the attacker outside the trust boundary taints a shared lookup (dns, arp, cache). the consumer has no reason to distrust the source.

this was not that.

the attackers got inside layerzero's trust boundary. they accessed the rpc list, compromised two nodes the dvn depended on, and swapped the op-geth binaries. that's an infra breach within the perimeter. supply-chain shaped, not network shaped.

and the payload was surgical. the malicious binary cloaked by ip, served forged payload only to the dvn, told the truth to scan and every other caller, then self-destructed to wipe logs and binaries.

rpc poisoning makes it sound like something that happened to the infra from the outside. the real story is a targeted implant operating inside the trust boundary.

that's a meaningfully scarier attack than the label suggests.

[RustyRabbit @_RustyRabbit]

@koeppelmann @lex_node Isn't a "security council" just another form of goverment though? Mabye a good way of looking at it is that you choose the government you enter into when bridging to an L2.
We do however need clear expectations as to the boundaries regarding socializing bad debt across bridges.

[RustyRabbit @_RustyRabbit]

@tayvano_ Yeah not only spoof the primary rpc, but also DoSsing the secondary.

[RustyRabbit @_RustyRabbit]

@tayvano_ @lex_node @senamakel @KelpDAO @LayerZero_Core Add to that an optimistic L2, and I wonder if it's possible to get a malicious Tx on L2 into the state update on L1 before the L2 checks the fraud proof

[RustyRabbit @_RustyRabbit]

@banteg Could 308 (and 309) have been reorged out at Unichain side?

[RustyRabbit @_RustyRabbit]

@storming0x @banteg I was wondering how they'd go from "our next model is so sophisticated we have to censor it " to this our next public model.

I guess the word is neutered.

[Nick Percoco @c7five]

Kraken Security Update

We are currently being extorted by a criminal group threatening to release videos of our internal systems with client data shown if we do not comply with their demands. It’s important to start with the most important points: our systems were never breached; funds were never at risk; we will not pay these criminals; we will not ever negotiate with bad actors.

Kraken identified and shut down two instances of inappropriate access to limited client support data.

In February 2025, we received a tip from a trusted source regarding a video shared on a criminal forum that appeared to show access to our client support systems. We immediately launched an investigation and quickly identified the individual involved as a member of our support team. Their access was revoked immediately, a full investigation was conducted, additional security controls were put in place and a limited number of affected clients were notified.

Since then, we have been collaborating with industry partners and law enforcement to investigate and disrupt insider recruitment efforts targeting not only crypto companies, but also gaming and telecommunications organizations.

More recently, we received another tip, along with a new video showing similar activity. We quickly identified the individual involved and terminated their access. As before, we acted immediately to revoke access, conduct a full investigation, and notify the small number of affected clients.

Across both incidents, only a very small number of client accounts were potentially viewed - approximately 2,000 in total (0.02% of clients).

Shortly after access was terminated, we began receiving extortion demands. The criminals threatened to distribute materials from both the February 2025 incident and the recent incident to media outlets and on social media if we did not comply. We will not pay these criminals.

Based on intelligence gathered across both incidents, along with extensive ongoing analysis, we believe there is sufficient evidence to support the identification and arrest of those responsible.

We are actively working with federal law enforcement across multiple jurisdictions to pursue all individuals involved and bring them to justice.

Due to the ongoing investigation, we cannot share additional details at this time. However, anyone with relevant information is encouraged to contact us directly.

The security of our clients is our highest priority, and we remain fully committed to combating the growing global threat of insider recruitment and constantly enhancing our security practices to combat new threats.

Note: If you are a client potentially affected by this, you've already been notified.

[RustyRabbit @_RustyRabbit]

@PatrickAlphaC What about an unrelated standalone mobile app acting as a proxy to scan the qr code, do the nested decoding and present it to the hardware wallet (instead of it directly scanning from MM)?
Wondering if it's possible to create a snap that sends it to the app via WalletConnect

[RustyRabbit @_RustyRabbit]

@0xRajeev Increased occurrence of high profile attacks always meant security budgets I creased the years after.

[Andrej Karpathy @karpathy]

- Drafted a blog post
- Used an LLM to meticulously improve the argument over 4 hours.
- Wow, feeling great, it’s so convincing!
- Fun idea let’s ask it to argue the opposite.
- LLM demolishes the entire argument and convinces me that the opposite is in fact true.
- lol

The LLMs may elicit an opinion when asked but are extremely competent in arguing almost any direction. This is actually super useful as a tool for forming your own opinions, just make sure to ask different directions and be careful with the sycophancy.

[Pashov Audit Group @PashovAuditGrp]

security auditors only have 5 moods:

1. fk I hit the Claude limit again
2. how we gonna get rich
3. random 2 am motivation
4. intense loneliness
5. my family needs me

[Hari @hrkrshnn]

"The language models we have now are the most significant thing to happen to security since the beginning of the internet".

Nicolas Carlini from Anthropic.

Full video below:

[RustyRabbit @_RustyRabbit]

@DevDacian @milotruck @nisedo_ Tragedy of the commons at work'