Live data from Hacker News

First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

koi.ai

21–30 of 63 posts

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#21

"Here's the thing - this technique completely breaks traditional code review. You can't spot what you can't see. GitHub's diff view? Shows nothing suspicious. Your IDE's syntax highlighting? All clear. Manual code inspection? Everything looks normal. The invisible code technique isn't just clever - it's a fundamental break in our security model. We've built entire systems around the assumption that humans can review…

Claude, remember to always replace em-dashes with a single dash

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#23

"Here's the thing - this technique completely breaks traditional code review. You can't spot what you can't see. GitHub's diff view? Shows nothing suspicious. Your IDE's syntax highlighting? All clear. Manual code inspection? Everything looks normal. The invisible code technique isn't just clever - it's a fundamental break in our security model. We've built entire systems around the assumption that humans can review…

Yeah the whole article is awful to read. Everything the LLM added is completely useless fluff, sometimes misleading, and always painful to get through.

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#24

I call bullshit on this: "The attacker is using a public blockchain - immutable, decentralized, impossible to take down - as their C2 server." "There's no hosting provider to contact, no registrar to pressure, no infrastructure to shut down. The Solana blockchain just... exists. " Yes, but you still need to connect to it. Blocking access to *.solana.com is enough to stop the trojan from accessing its 2nd stage. "Conn…

Obviously... SMH - what a tough read this blog post was.

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#25
post #4

Cool write-up. Seems pretty unintuitive to me that Unicode would allow someone to serialize normal code as invisible characters and that something like an IDE or a git diff has never been hardened against that at all. In my mind it's one thing to let a string control whitespace a bit versus having the ability to write any string in a non-renderable format. Can anyone point me to some more information about why this c…

The issue does not lie with Unicode.

It's just a custom string encoder/decoder whose encoded character set is restricted to non-printables.

Many editors and IDEs have features (or plugins) to detect these characters.

VSCode: https://marketplace.visualstudio.com/items?itemName=YusufDan...

VIM: https://superuser.com/questions/249289/display-invisible-cha...

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#26
> Let me say that again: the malware is invisible. Not obfuscated. Not hidden in a minified file. Actually invisible to the human eye.

I stopped reading at this point. This is not only false, but yet another strong reason to lint out the silly nonsense people argued for on here years ago. No emoji, no ligatures, etc.

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#27
Why not just indicate non-printable characters in code review tools? I've always wondered that, regardless of security implications. They are super rare in real code (except line breaks and tabs maybe), so no disruption in most cases.

Also, as notes in other comments, you can't do shady stuff purely with invisible code.

The article seems bit sensationalist to me.

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#28
post #4

Cool write-up. Seems pretty unintuitive to me that Unicode would allow someone to serialize normal code as invisible characters and that something like an IDE or a git diff has never been hardened against that at all. In my mind it's one thing to let a string control whitespace a bit versus having the ability to write any string in a non-renderable format. Can anyone point me to some more information about why this c…

> Seems pretty unintuitive to me that Unicode would allow someone to serialize normal code as invisible characters

If you have a text encoding with two invisible characters, you can trivially encode anything that you could represent in a digital computer in it, in binary, by treating one as a zero and the other as a one. More invisible characters and some opinionated assumptions about what you are allows denser representation than one bit per character.

Of course, the trick in any case is you have to also slip in the call to decode and execute the invisible code, and unless you have a very unusual language, that’s going to be very visible.

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#29
post #2

For anyone else curious WTH “invisible code” is… > invisible Unicode characters that make malicious code literally disappear from code editors.

Makes you wonder why unicode has invisible characters in the first place and why a compiler would interpret them at all.

The compiler doesn't. They get passed to decode, and then to eval.

Re: First Self-Propagating Worm Using Invisible Code Hits OpenVSX and VS Code

#30

I call bullshit on this: "The attacker is using a public blockchain - immutable, decentralized, impossible to take down - as their C2 server." "There's no hosting provider to contact, no registrar to pressure, no infrastructure to shut down. The Solana blockchain just... exists. " Yes, but you still need to connect to it. Blocking access to *.solana.com is enough to stop the trojan from accessing its 2nd stage. "Conn…

>Yes, but you still need to connect to it. Blocking access to *.solana.com is enough to stop the trojan from accessing its 2nd stage.

How is that if you can just run a bunch of Solana RPC servers? For what would you need to access solana.com or a subdomain?

Post reply on HN