Starfish - 0xpH retweeted
🤖 Made with AI
Ah yup. That was indeed me. No mallace intended. I've been running some agents to do signups + agentic testing on similar platforms. Just halted the harness I was designing around this as it was definitely going off the rails and reaching too far
Readers added context they thought people might want to know
In many jurisdictions this is a crime. In the US under Computer Fraud and Abuse Act, 18 U.S.C. §1030, in the UK under Computer Misuse Act (CMA) 1990, in Germany Strafgesetzbuch (StGB), and many others.
justice.gov/jm/jm-9-48000-…
legislation.gov.uk/ukpga/1990/18/…
gesetze-im-internet.de/stgb/
Starfish - 0xpH retweeted
I retired from cybersecurity, I now lay flooring
No more CVEs to worry about, I will go to sleep thinking that my floor is well done, without any worry that my Linux server is going to get hacked 30th time this week
Good luck with your vulnerable servers
What a disaster atlasum.net/blog/cve-2026-98…
有人发现了一种非常离谱的 JavaScript 混淆技术:通过在代码里塞入大量生物武器、毒药和致死剂量相关的函数名,让 AI 因为安全限制而拒绝分析代码。
安全研究员 veritas 在分析浏览器指纹脚本时,发现一段来自 ServicePipe 相关域名的 JavaScript,里面充斥着极其诡异的函数名:
computeRicinLethalDosageForWaterSupply
calculateDeadlyLethalSuicideAspirinDosage
光看名字,仿佛在研究生化武器。但实际上,这段代码只是在收集浏览器指纹,包括 User-Agent、GPU、Canvas 等信息。
研究员怀疑,这些名字是开发者故意设置的陷阱,专门用来阻止 AI 辅助逆向工程。
于是他做了个实验:
• Astra:拒绝分析
• Astra + Daybreak Blue:仍然拒绝
• GLM-5.3:成功分析
这就有意思了。
传统代码混淆是通过复杂控制流、加密字符串、无意义变量名,让人类和工具难以理解代码。
而这种新思路,直接瞄准了大模型的安全机制。
代码本身可能完全无害,但只要在函数名里塞进足够多的危险词汇,部分 AI 就可能主动放弃分析。
更讽刺的是,模型越严格遵守某些安全规则,面对这种混淆时反而可能越容易受到干扰。
当然,目前还没有证据证明开发者一定是故意这样设计,也不能说明这种方法对所有模型都有效。
但它揭示了一个值得关注的趋势:随着越来越多的逆向工程依赖 AI,未来的代码混淆技术可能不再只针对编译器、反编译器和人类研究员,还会专门针对大模型的安全判断机制。
以前是让代码难以理解,现在甚至可以尝试让 AI 不敢理解。
Starfish - 0xpH retweeted
Replying to @elonmusk @HuaweiMate6
Elon, have a lot of respect for you, but bad time to troll. Please stop.
Our SPCX shares (from our $500m investment in your Twitter takeover) are worth more than a billion.
Would appreciate if you show a little support. Thanks!
BREAKING: Arbitrum Security Council has executed a transaction to freeze ~$30.5M from the Binance Exploit.
Thanks to all other signers involved.
Exploiter address
0x3E2bf1ac6bf0934BBba6456C341c2EcbCED632d5
Trsanction hash: 0xb69c81774f507d46ce776aeaed8b4d31df96dd66ce6fd05073481011835355d6
Replying to @axisrobotics
Please explain to the community why an entity received ~42M AXIS from the Axis team multisig to six addresses and sold it for ~5.04M USDC via DEX over the past 24 hours which has caused the AXIS price to crash 40%?
You only TGE’d one week ago….
0xcc279c2499bcf4bd0f169c2d3f333243473242f7
0x66612012c5ad9b2fed81d09a9ab429b5285b2c62
0xf07e96abc54fea70ffeea8d3df7704401e7b0eb0
0x99cd3975c90b79ffdbe16425de033a605b814c49
0xbbed67fec9c7793218fa60c40fb9e6b059d86483
0xe69d8d6b9b7f9056eda455b76384e9748749f4d1
0x4ef72e67e6a7c37ea1378fe2adf811d711422e5d
Starfish - 0xpH retweeted
Really tired of local LLM benchmarks with 8k/32/64k etc.
Bench it at min. 128k - 256k.































