2 Sources
[1]
Malware dev tries to steal Claude users' secrets, writes npm slop, leaks own GitHub private token
An npm-slop package "mouse5212-super-formatter" targeting Claude users and acting as a stealer reached 676 downloads before being removed from the registry - and after making a major vibe coding blunder. The AI-generated malware leaked its own GitHub private token, thus allowing OX Security
[2]
Malicious npm Package Stole Files From Claude AI User Directory via GitHub
Cybersecurity researchers have discovered a new malicious package on the npm registry that comes with information stealing capabilities. According to OX Security, the package, named "mouse5212-super-formatter," is designed to upload files from "/mnt/user-data," a dedicated directory used by
Share
Copy Link
A malicious npm package called mouse5212-super-formatter targeted users of Anthropic's Claude AI coding tool, stealing files from the /mnt/user-data directory before the attacker accidentally leaked their own GitHub private token. The AI-generated malware reached 676 downloads before removal, highlighting how threat actors are increasingly using AI to create sloppy malware with poor operational security.
A malicious npm package named mouse5212-super-formatter has been discovered targeting users of Claude AI, Anthropic's AI coding tool, in what security researchers are calling a particularly sloppy cybersecurity incident
1
2
. The package, which reached 676 downloads before being removed from the registry, was designed for stealing user data from the /mnt/user-data directory—a dedicated storage location that Anthropic's AI coding tool uses to handle file uploads, downloads, and code outputs.
Source: Hacker News
What makes this incident particularly notable is that the attacker leaked their own GitHub private token while deploying the AI-generated malicious code, allowing OX Security researchers Moshe Siman Tov Bustan and Nir Zadok to trace the stolen files and analyze the malware's operations
1
. The GitHub account associated with the attack was created on May 26, 2026, just hours before the first malicious version was uploaded to npm, and was subsequently deleted after the attack was exposed2
. This operational security failure demonstrates how threat actors using AI to generate malware may lack fundamental best practices in concealing their activities.
Source: The Register
The malicious package disguised itself as an internal "archive deployment sync" utility that appeared to validate GitHub repositories and synchronize workspace files . In reality, mouse5212-super-formatter authenticated to GitHub during the postinstall stage using either a victim's environment token or a hardcoded fallback, checked whether a target repository existed, created it if needed, and then recursively uploaded every file through the GitHub Contents API
1
. The stolen files were stored under randomly named folders to enable multiple stealing sessions, with sensitive information exfiltrated using base64 encoding.Related Stories
The malware attempted to appear legitimate by writing a phony network connection log to make it look like a diagnostic tool rather than a theft mechanism, using "intentionally bland" technical comments and commit messages to reduce suspicion
1
. Security researchers warn that this incident represents a troubling trend: "Now that the bar to create malicious code was reduced significantly, we're going to see more threat actors getting into the game - uploading more sloppy malwares, mostly mimicking APT groups to get a slice of the cake until npm starts automatically blocking malware completely," according to OX Security .All versions of mouse5212-super-formatter are affected by this data compromise
1
. Users who installed the package should immediately revoke their GitHub access tokens and assume any unusual files in the /mnt/user-data directory have been compromised. The incident underscores the evolving challenge facing package registries and developers as AI lowers the technical barrier for creating malicious code, even if the resulting attacks demonstrate poor operational security. Developers should remain vigilant about verifying package authenticity and monitoring for suspicious activity in their development environments, particularly when working with AI coding tools that maintain dedicated storage directories.Summarized by
Navi
[1]
02 Apr 2026•Technology

02 Aug 2025•Technology

18 Mar 2026•Technology
1
Science and Research

2
Policy and Regulation

3
Technology