Act this weekWhat happenedHackers hid huge malware files in 42 hijacked GitHub projects that run when the project is opened in tools like Claude, Gemini, Cursor or VS Code.
Who is affectedDevelopers and companies using GitHub, npm, Claude, Gemini, Cursor or VS Code, especially anyone who opened affected projects.
What to do- 1Check your projects for a .github/init.js file and for unexpected startup settings in AI tool and VS Code files.
- 2Remove the malicious package versions and rebuild affected computers from trusted sources.
- 3Remove the net-health-checker and pkg-runtime persistence first, then change GitHub, npm, cloud, SSH and AI account credentials.
- 4Read each repository's file list directly instead of relying on GitHub search, which missed these files.
Hackers have planted malware in 42 real GitHub projects, and the trap can spring when a developer simply opens one in an AI coding tool. Claude, Gemini, Cursor and VS Code are all affected. The projects belong to 11 legitimate owners, including individual developers, students and one company.
What happened
GitHub is a popular site where people store and share code. The attackers hid a script in a file named .github/init.js. Small settings files for each tool call that script when a session starts or a folder opens. No clever trick on the user is needed. The attack uses startup steps the tools already trust.
Researchers at JFrog Security Research found the projects while studying an npm worm they call the "testmetest" campaign. npm is a library of code packages that developers download. Another firm, SafeDep, described the npm side on October 22 and reported no confirmed victims.
Why it was hard to spot
The hidden file is huge, between 12.9 MB and 13.7 MB. GitHub search did not index files that big, and the files looked empty at first. JFrog's first sweep found 26 projects. Reading the project file lists directly raised the count to 42.
The attacker also faked history. On September 28, scripted batches copied old commit messages and dates from real history, so the activity looked much older than it was. JFrog says the goal was to turn stolen GitHub and npm access into new malicious releases, which then steal more access.
Who it affects
Developers and companies that use GitHub, npm, Claude, Gemini, Cursor or VS Code are the main targets, especially anyone who opened an affected project. If you run a business that relies on outside developers, ask whether they open code from GitHub in these tools. People who do not work with code are not directly exposed.
One related finding is less clear. JFrog found scanner tools in the same hijacked accounts that look for cPanel and WHM systems with a known flaw. It found no proof that any cPanel server was actually breached.
What to do
The alert box above lists the steps. One detail matters most: the worm contains a wiper that triggers when a stolen token is revoked. So remove its persistence files first, then change passwords and keys.
What happens next
More hijacked projects may turn up, since the first search missed 16 of them. Until then, treat any unfamiliar project as untrusted before opening it in an AI tool.
The takeawayDo not open unfamiliar GitHub projects in AI coding tools, and check your own for a .github/init.js file before changing any passwords.