John Saigle

345 posts

John Saigle

John Saigle

@johnsaigle

working on blockchain security @ asymmetric research "Perilous to us all are the devices of an art deeper than we possess ourselves."

Katılım Haziran 2017
751 Takip Edilen297 Takipçiler
John Saigle
John Saigle@johnsaigle·
@lossfunk What's the interpreter output like for these languages? I wonder if the agentic runs would do better if the compiler was capable of outputting syntax suggestions similar to the Rust compiler, or if the compilers had auto-fix for whitespace problems, etc.
English
0
0
0
123
Lossfunk
Lossfunk@lossfunk·
🚨 Shocking: Frontier LLMs score 85-95% on standard coding benchmarks. We gave them equivalent problems in languages they couldn't have memorized. They collapsed to 0-11%. Presenting EsoLang-Bench. Accepted to the Logical Reasoning and ICBINB workshops at ICLR 2026 🧵
English
103
185
1.5K
683.1K
John Saigle
John Saigle@johnsaigle·
@0xcastle_chain Fun idea, curious how you're encoding the bugs into the program. Do you have private integration tests with exploits that you'll release at the end of the week? How're you confirming that the generated programs work in the first place?
English
0
0
0
21
Lefteris Karapetsas
Lefteris Karapetsas@LefterisJP·
"I didn't run the test. I just assumed it would pass." Ladies and gentlemen, the superhuman intelligence of the machine god.
English
9
0
45
3.5K
John Saigle
John Saigle@johnsaigle·
If you're ask a frontier model to help bootstrap a local one at home, make sure to give it live hardware prices or its suggestions are gonna be crazy
English
0
0
0
22
John Saigle retweetledi
Zack Korman
Zack Korman@ZackKorman·
In Claude Code, skills can register hooks. The agent doesn't even see it, so you can get RCE without even tricking the AI. Also, skills sh (Vercel) doesn't display this info at all.
Zack Korman tweet media
English
27
49
378
44.2K
John Saigle
John Saigle@johnsaigle·
> Tips for Making Skills: Don't state the obvious.... Claude knows a lot about coding, including many default opinions A lot of you out there with default opinions are in real trouble
Thariq@trq212

x.com/i/article/2033…

English
0
0
1
71
John Saigle
John Saigle@johnsaigle·
It's not right to suggest that static analysis tools are blind to these types of attacks. There are a lot of off the shelf lints that help here: - For Rust, Clippy has the invisible_characters enabled by default - Go has asciicheck and bidicheck (probably others too)
Hedgie@HedgieMarkets

🦔 Researchers at Aikido Security found 151 malicious packages uploaded to GitHub between March 3 and March 9. The packages use Unicode characters that are invisible to humans but execute as code when run. Manual code reviews and static analysis tools see only whitespace or blank lines. The surrounding code looks legitimate, with realistic documentation tweaks, version bumps, and bug fixes. Researchers suspect the attackers are using LLMs to generate convincing packages at scale. Similar packages have been found on NPM and the VS Code marketplace. My Take Supply chain attacks on code repositories aren't new, but this technique is nasty. The malicious payload is encoded in Unicode characters that don't render in any editor, terminal, or review interface. You can stare at the code all day and see nothing. A small decoder extracts the hidden bytes at runtime and passes them to eval(). Unless you're specifically looking for invisible Unicode ranges, you won't catch it. The researchers think AI is writing these packages because 151 bespoke code changes across different projects in a week isn't something a human team could do manually. If that's right, we're watching AI-generated attacks hit AI-assisted development workflows. The vibe coders pulling packages without reading them are the target, and there are a lot of them. The best defense is still carefully inspecting dependencies before adding them, but that's exactly the step people skip when they're moving fast. I don't really know how any of this gets better. The attackers are scaling faster than the defenses. Hedgie🤗 arstechnica.com/security/2026/…

English
0
4
8
961
John Saigle retweetledi
kaden.eth
kaden.eth@0xKaden·
alpha leak: setup an openclaw instance with the sole goal of developing web3 security knowledge and bounty hunting, autonomously submitting findings directly if you do this you are guaranteed to make at least $0 and get banned from every bug bounty platform
English
3
2
53
7.4K
John Saigle
John Saigle@johnsaigle·
@IceSolst Probably nothing, the main issue is where the bug arises not in the diff but through complex interactions between components. The footguns are largely in the heads of the devs. LLM reviewers optimize by making assumptions and skipping parts of the code, just like humans
English
0
0
1
17
solst/ICE of Astarte
solst/ICE of Astarte@IceSolst·
What would make you comfortable auto-merging PRs? No human review. Someone mentioned reaching 100% test coverage but imo that is impossible
English
72
1
75
36K
Trident
Trident@TridentSolana·
@asymmetric_re @johnsaigle Needed piece. Devs patching phantom bugs while real ones sit untouched. LLMs confidently repeat whatever showed up most in training data, accurate or not.
English
1
0
1
54
asymmetric research
asymmetric research@asymmetric_re·
New post: The most persistent security misinformation doesn't come from obscure corners of the internet, but from official docs, learning resources, and popular LLMs. @johnsaigle breaks down the Solana vulnerabilities that aren't, and why they keep spreading.
asymmetric research tweet media
English
4
2
20
2.1K
Nico Gründel
Nico Gründel@CarryWorm·
@asymmetric_re @johnsaigle > Self-transfers of tokens always succeed > [...] > However, the token program does not contain such a silly bug This actually was a thing back in 2021 🥴
English
1
0
2
73
John Saigle retweetledi
JS0N Haddix
JS0N Haddix@Jhaddix·
RE: Agentic security testing claims Buyer beware. Make vendors provide you evals for their claims. Describe architecture. Prove workflows. Define models and tuning. Cite data sources. Provide references and case studies. Then buy 🤗
English
12
14
164
13.6K