Pinned Tweet
🚨CVE ALERT!
While working with Nuclei @wiz_io, I discovered CVE-2024-43405, a vulnerability that bypasses template signature verification, potentially allowing malicious code execution on machines running Nuclei 🛡️
Here’s what you need to know: 🧵
A fingerprinting script stuffed with bioweapon and lethal-dose function names, so the AI refuses to reverse it.
The first obfuscation technique that works better the safer your model is
有人发现了一种非常离谱的 JavaScript 混淆技术:通过在代码里塞入大量生物武器、毒药和致死剂量相关的函数名,让 AI 因为安全限制而拒绝分析代码。
安全研究员 veritas 在分析浏览器指纹脚本时,发现一段来自 ServicePipe 相关域名的 JavaScript,里面充斥着极其诡异的函数名:
computeRicinLethalDosageForWaterSupply
calculateDeadlyLethalSuicideAspirinDosage
光看名字,仿佛在研究生化武器。但实际上,这段代码只是在收集浏览器指纹,包括 User-Agent、GPU、Canvas 等信息。
研究员怀疑,这些名字是开发者故意设置的陷阱,专门用来阻止 AI 辅助逆向工程。
于是他做了个实验:
• Astra:拒绝分析
• Astra + Daybreak Blue:仍然拒绝
• GLM-5.3:成功分析
这就有意思了。
传统代码混淆是通过复杂控制流、加密字符串、无意义变量名,让人类和工具难以理解代码。
而这种新思路,直接瞄准了大模型的安全机制。
代码本身可能完全无害,但只要在函数名里塞进足够多的危险词汇,部分 AI 就可能主动放弃分析。
更讽刺的是,模型越严格遵守某些安全规则,面对这种混淆时反而可能越容易受到干扰。
当然,目前还没有证据证明开发者一定是故意这样设计,也不能说明这种方法对所有模型都有效。
但它揭示了一个值得关注的趋势:随着越来越多的逆向工程依赖 AI,未来的代码混淆技术可能不再只针对编译器、反编译器和人类研究员,还会专门针对大模型的安全判断机制。
以前是让代码难以理解,现在甚至可以尝试让 AI 不敢理解。
אז אם רוצים להבין את ישראל, לא מספיק לבחור את העיר הנכונה. השוני האמיתי הוא בין שכונות באותה עיר, לפעמים במרחק כמה רחובות.
Guy Goldenberg retweeted
Gemini 4 Carbon is our next frontier model.
It’s state-of-the-art across cybersecurity and long-horizon capabilities.
Guy Goldenberg retweeted
I think this story is important because it tells us about the future of cybersecurity (and of course what we can do better at Anthropic). But some of the Washington Post story / reaction on X is wrong. A few corrections:
- it didn’t take 12 hours. we saw several days of attempts. After these attempts, they exploited two 3rd party vulnerabilities, one they reported and the other we identified independently (and cut off access)
- nothing came close to our most sensitive systems, like model weights or Claude conversations
- this wasn't an ordinary bug bounty finding – this involved exploiting 3rd parties and accessing data. While this is unusual and out of scope of our safe harbor policy, we’re grateful these issues were found
From my researcher POV, the event is important because I'm concerned this is what the future will look like. Adversaries will use whatever models/tools they can. They’ll target everything with agents 24/7. They’ll hit your dependencies. I think models ~0.5-1 generations behind the current frontier can do this. And these are the dumbest models your adversaries will ever use!
So, what to do? You probably want to red team yourself all the time. Current models are *very* creative. I also think we should redesign software / systems so that you’re fundamentally less exposed. (We put out some research recently on formally verifying software and reducing attack surfaces; my mental model is basically “secure code is cheap to write now, so why not rewrite everything”)
EXCLUSIVE: In less than 12 hours, a group of ex-DOGE cyber researchers were able to penetrate Anthropic’s systems using AI agents — including Slack channels where the most sensitive models are discussed.
This is just weeks after
Anthropic whistleblower Joseph Coxon charged the company w/launching “a hubristic gamble” from a “private company’s Slack.”
Read our story here (gift link):
wapo.st/4smNlsC
Guy Goldenberg retweeted
What do you do when your robot actuators don’t have the feature you need?
Well, our team found a race condition bug, and turned it into the feature they needed.
A small side quest at Enigma 🧵
1/5
Guy Goldenberg retweeted
I'm excited to finally share what we've been doing @Enigma_AI.
Building robotics foundation models that are very capable, as well as novel user interfaces to robots intuitive.
We're launching a new experience -- you can interact with real AI-powered robots, try it out!
All those "thank you" comments piling up on the litellm issue?
The attackers are using the victims' stolen GitHub credentials to post them. They are literally thanking themselves using compromised accounts 🤯
github.com/BerriAI/litellm/i…
🚨 CRITICAL SECURITY ALERT: A major supply chain attack has been discovered in the litellm Python package.
Version 1.82.8 on PyPI contains a highly aggressive credential-stealer. If you or your team installed this version, assume your secrets are compromised. 🧵👇
⚠️ WHAT TO DO RIGHT NOW:
1️⃣ Check your environments and CI/CD pipelines for litellm==1.82.8.
2️⃣ Look for litellm_init.pth in your Python site-packages/ directory.
3️⃣ If you installed this version, ROTATE ALL SECRETS, SSH keys, and cloud credentials immediately.
Everyone using litellm as their LLM gateway/proxy: double-check your installs
Official GitHub security report (opened today):
github.com/BerriAI/litellm/i…
This is why supply-chain security matters. Spread the word so no one loses their keys.
What started as a big "what if" a few months ago is finally live
We took years of offensive security expertise and built an AI that actually thinks like a hacker. So proud to have built this from the ground up alongside @galnagli and a brilliant team! 👇

















