June 8, 2026
Open folder, unleash chaos
Config Files That Run Code: Supply Chain Security Blindspot
That harmless settings file might be a trap, and commenters are absolutely done with it
TLDR: A new warning says ordinary-looking settings files can make coding tools run malicious commands the moment a project is opened, helping thieves steal passwords and cloud secrets. Commenters split between grim “we’ve warned about this for years” frustration and jokes that software companies keep calling dangerous behavior a feature.
The big freakout here is brutally simple: you can download a coding project, open the folder, and your own tools may run attacker code before you’ve even looked around. Not because of some shady add-on, but because a plain-looking settings file quietly tells apps like VS Code, Cursor, Claude Code, Gemini CLI, npm, Composer, or Bundler to fire off a command. In the example at the center of the drama, one sneaky commit slipped a giant hidden program into a repo, then used a bunch of tiny config files to launch it. That program allegedly hunted for cloud passwords, coding tokens, and other secrets, then shipped them off to public GitHub repos. Cute! Terrifying, but cute.
And the comments? Pure exhausted rage with a side of tinfoil comedy. One user wondered if Windows Defender has been trying to snitch on their config file to Microsoft this whole time, joking that Redmond might be extra curious because it involves rival tools. Another commenter was less jokey and more workplace panic: they’ve got junior developers using VS Code and now finally have a scary article to wave in front of them. But the spiciest mood came from the security old guard, who basically shouted, “This is not a blind spot — people have been screaming about it for years, and nobody cares until disaster hits.” Then came the darkest punchline of all: maybe this isn’t a bug, it’s a feature — the same cursed energy as apps that treat random files and links like invitations to execute something. The vibe is half public service announcement, half group therapy, with a strong undercurrent of how is this still normal?
Key Points
- •The article says repository config files in tools such as VS Code, Cursor, Claude Code, Gemini CLI, npm, Composer, and Bundler can act as code-execution triggers rather than passive metadata.
- •It uses the Miasma worm as an example, citing commit `f72462d9` in `icflorescu/mantine-datatable`, where five added files launched a sixth dropper file, `.github/setup.js`.
- •According to the article, SafeDep documented the incident and reported 121 affected repositories, while this post focuses specifically on the config-file execution surface.
- •The dropper file is described as a 4,348,254-byte obfuscated script that stays above GitHub code search’s approximate 384 KB indexing limit and decodes into a Bun loader that AES-decrypts a credential stealer.
- •The seven launcher configs do not contain the payload; they each invoke `node .github/setup.js`, using developer tools’ own hook or rule mechanisms to execute the malware.