# jscrambler-npm-package-hijacked-to-drop-ai-config-infostealer: jscrambler npm Package Hijacked to Drop AI Config Infostealer

> jscrambler npm Package Hijacked to Drop AI Config Infostealer is a critical-severity supply chain compromise issue in jscrambler, a MCP server. Affected: 8.14.0 || 8.16.0 || 8.17.0 || 8.18.0 || 8.20.0.

- **Canonical URL:** https://catalog.anomity.ai/vuln/jscrambler-npm-package-hijacked-to-drop-ai-config-infostealer
- **Aliases:** ti-051
- **Severity:** critical
- **Attack type:** Supply chain compromise, Credential theft
- **Component:** jscrambler (MCP server)
- **Package:** jscrambler (npm)
- **Exploited in the wild:** no known exploitation
- **Published:** 2026-07-11
- **Last verified:** 2026-11-01
- **JSON:** https://catalog.anomity.ai/api/entries/vuln/jscrambler-npm-package-hijacked-to-drop-ai-config-infostealer

## Summary

An attacker used a stolen credential to push malicious jscrambler npm versions carrying a cross-platform Rust infostealer via a preinstall hook. The malware specifically sweeps AI coding tool config files for Claude Desktop, Cursor, Windsurf, VS Code, and Zed, where API keys and MCP server credentials sit, alongside cloud keys and wallets.

## Affected versions

| Affected | Fixed in |
| --- | --- |
| 8.14.0 \|\| 8.16.0 \|\| 8.17.0 \|\| 8.18.0 \|\| 8.20.0 | no fixed version listed |

## Am I affected by this vulnerability?

You are affected if you run jscrambler 8.14.0 || 8.16.0 || 8.17.0 || 8.18.0 || 8.20.0.

## How do I fix it?

Move off jscrambler 8.14.0 through 8.20.0 to 8.22.0, rotate cloud, npm, and AI tool API keys, and block C2 IPs 37.27.122.124 and 57.128.246.79.

## How do I find every machine running jscrambler?

Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run jscrambler and which version, then enforce a policy on it.

## References

- article: https://thehackernews.com/2026/07/compromised-jscrambler-8140-npm-release.html

## Related vulnerabilities

- [tensorlake-npm-sdk-0-5-144-compromised-by-a-shai-hulud-chaindrop-worm](https://catalog.anomity.ai/vuln/tensorlake-npm-sdk-0-5-144-compromised-by-a-shai-hulud-chaindrop-worm) — critical
- [shai-hulud-wave-c-payload-returns-after-111-days-including-feishu-docx](https://catalog.anomity.ai/vuln/shai-hulud-wave-c-payload-returns-after-111-days-including-feishu-docx) — critical
- [deadbugz-an-mcp-server-that-behaves-for-exactly-three-tool-calls-then](https://catalog.anomity.ai/vuln/deadbugz-an-mcp-server-that-behaves-for-exactly-three-tool-calls-then) — critical
- [shai-hulud-reaches-the-official-mcp-registry-shipping-poisoned-claude](https://catalog.anomity.ai/vuln/shai-hulud-reaches-the-official-mcp-registry-shipping-poisoned-claude) — critical
- [forever-security-an-agents-md-planted-in-downloads-got-codex-to](https://catalog.anomity.ai/vuln/forever-security-an-agents-md-planted-in-downloads-got-codex-to) — high
- [litellm-1-107-0-compromised-on-pypi-and-docker-a-cook-pth-startup-hook](https://catalog.anomity.ai/vuln/litellm-1-107-0-compromised-on-pypi-and-docker-a-cook-pth-startup-hook) — critical

---

Source: Anomity Security Database (https://catalog.anomity.ai/vuln). Detect affected AI tools on developer devices: https://anomity.ai/?utm_source=catalog&utm_medium=vuln-md&utm_campaign=jscrambler-npm-package-hijacked-to-drop-ai-config-infostealer