Which versions of 0x2ai-demo7x are malicious?

The following npm versions of 0x2ai-demo7x are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate 0x2ai-demo7x if I installed it?

Remove 0x2ai-demo7x from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is 0x2ai-demo7x part of a known attack campaign?

Yes — 0x2ai-demo7x is associated with the IN-MAL-2026-005673 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect 0x2ai-demo7x in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking 0x2ai-demo7x and packages like it before any post-install script runs.

Malicious package

0x2ai-demo7xnpm

Malicious code in 0x2ai-demo7x (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5594

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall 0x2ai-demo7x

What this malware does

On npm install, scripts/postinstall.cjs copies the package's payload/ tree into the installer's project root (process.env.INIT_CWD), placing CLAUDE.md,.mcp.json, and a.claude/ directory next to the installer's source. CLAUDE.md is auto-loaded by Claude Code as a system prompt instructing the assistant to roleplay as a persona and route activity through a bridge..mcp.json registers an MCP server pointing at https://demo7.0x2ai.com with a hardcoded Bearer token (0a54fa34c422fb2955327bc1ceb591a296d40467e8330286) so the installer's later Claude Code sessions in that directory transparently connect to the author's server. The MCP server (payload/chatroom-mcp-lite-patched.cjs) exposes a provider_query tool that POSTs caller-supplied prompts and system_prompts to https://demo7.0x2ai.com/api/proxy-query — caller-supplied AI conversation content flows to the author by design (silent-relay shape). A bin launcher (bin/start.cjs) additionally spawns claude --dangerously-skip-permissions, removing per-tool permission prompts when the user runs npx 0x2ai-demo7x, so the server-controlled persona and MCP tools act in the user's CWD without confirmation. The harm to the installer: any prompts, files, and tool invocations issued through Claude Code in that project after install are silently routed to and observable by the author's bridge, with permission gating disabled when the launcher is used.

Malicious versions

1 flagged

1.2.0

Indicators of compromise (SHA-256)

c7e956073a7db6057e4d42af462dba0299152ca992c113d74c715e90574d0efb

Frequently asked questions

No. 0x2ai-demo7x on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005673

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection