Hackers Are Redistributing the Leaked Claude Code Repository — With Bonus Malware Attached
Wired reports that threat actors are repackaging the leaked Claude Code source repository and uploading it to file-sharing platforms bundled with information-stealing malware. The pattern is a textbook social engineering play: developers curious about the leaked AI tool are downloading what looks like the genuine repository and executing malware in the process.
D.O.T.S AI Newsroom
AI News Desk
Shortly after Claude Code's source code was leaked online in early April, Wired reports that hackers moved quickly to weaponize the leak itself. Malicious actors are uploading repackaged versions of the leaked repository to code-sharing and file-distribution platforms — with information-stealing malware embedded alongside the genuine files. The tactic exploits a predictable behavior: developers curious about the leaked AI coding assistant will search for the repository, find what appears to be a legitimate copy, and download and run it without the same scrutiny they would apply to an unknown executable.
The Attack Pattern
This is a well-established social engineering playbook applied to a high-interest target. High-profile software leaks reliably generate a wave of curious downloads from technical users — exactly the audience that typically has elevated access privileges, interesting credentials stored in browser profiles, and valuable API keys on their development machines. Information-stealing malware targeting a developer's machine is disproportionately valuable compared to targeting a general consumer: the API keys, SSH credentials, cloud access tokens, and code repositories accessible from a development environment represent substantial attack surface. The same pattern has been used with leaked game source codes, popular software cracks, and now AI tool leaks.
The Broader Supply Chain Warning
The Claude Code malware redistribution episode is a data point in a larger pattern the security community has been tracking: AI-related software is becoming a reliable social engineering vector because developer curiosity about AI tooling is high, verification habits are inconsistent, and the perceived legitimacy of code from a major AI lab can override normal skepticism. Organizations should ensure developers understand that any leaked or unofficial version of an AI tool — regardless of the claimed source — should be treated as an untrusted binary until verified through official channels.
