Topic starter
02/08/2026 11:32 am
TL;DR: A live infostealer campaign is impersonating Claude Code, JetBrains, NotebookLM and other AI developer tools across 88 domains, with 32 still active and payloads stealing browser credentials, API keys, password vaults and crypto transactions, according to Straikerai reports. The campaign shows that trusted install paths, search visibility and terminal execution have become a credential-rich attack surface for AI developers.
Editorial analysis by NHI Mgmt Group, based on content published by Straikerai: “Fake Claude Code, Real Malware: Inside the Campaign Targeting AI Developers”.
By the numbers:
- The campaign was tracked across 88 domains on at least 10 hosting platforms.
- 32 of the 88 tracked domains were still active as of May 14, 2026.
- The attackers used 10 new GitHub Pages domains during the analysis window.
Key questions
Q: What breaks when developers copy install commands from fake AI tool pages?
A: The trust boundary fails at the moment copied text becomes executable code.
Q: Why do AI coding environments create more secret exposure risk than standard developer tools?
A: They can inspect repository context, read dotfiles, and infer where credentials are stored, then act on that information through commands or file changes.
Q: How can security teams tell when a fake install campaign is affecting developers?
A: Look for unusual combinations of search traffic, page redirects, terminal launches and new secret use shortly after tool installation.
Practitioner guidance
- Govern AI tool installation paths Restrict AI coding assistant onboarding to approved, verified sources and block ad hoc install instructions from untrusted search results or mirrors.
- Treat AI API keys as high-risk secrets Inventory API keys, tokens and vault material used by developer tools, assign clear owners and remove anything that is not needed for active work.
- Add install-time telemetry and correlation Correlate browser navigation, command execution and secret access around developer setup events so a fake docs visit can be tied to terminal activity.
Bottom line: AI developer workflows are now a malware delivery path because install-time trust can be abused before endpoint controls see a file.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 12:47 pm
AI developer trust has become a credential attack surface: the decisive risk is no longer only whether a tool is legitimate, but whether the onboarding path can be trusted end to end. Search results, documentation pages and terminal commands now function as identity-adjacent controls because they determine where credentials and tokens are introduced into the environment. Practitioners should treat install-time trust as part of governance, not user convenience.
A few things that frame the scale:
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
A question worth separating out:
Q: Should organisations block all AI tool installation from the open web?
A: They should at least require a controlled path for AI tool installation and treat open-web instructions as untrusted until verified. The goal is not to ban developer tooling, but to stop unauthorised onboarding from becoming a malware delivery path. Approval, provenance checks and fast revocation matter more than convenience here.
👉 Read our full editorial: Fake Claude Code malware shows how AI developer trust becomes attack surface