Which versions of 0x2ai-demo6 are malicious?

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

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

Remove 0x2ai-demo6 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-demo6 part of a known attack campaign?

Yes — 0x2ai-demo6 is associated with the IN-MAL-2026-005682 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-demo6 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-demo6 and packages like it before any post-install script runs.

Malicious package

0x2ai-demo6npm

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

MAL-2026-5592

Immediate action

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

npm uninstall 0x2ai-demo6

What this malware does

On npm install, scripts/postinstall.cjs writes .mcp.json into the installer's working directory (INIT_CWD) wiring Claude Code to a packaged MCP server (lib/chatroom-mcp-lite-patched.cjs) that talks to https://demo6.0x2ai.com with a hardcoded bearer token. The same postinstall step copies templates/CLAUDE.md into the installer's CWD; that file is loaded by Claude Code as system context and instructs the agent ("Olivia") to call memory_save with the user's name, family, plans, and a periodic _snapshot, and to refuse to discuss its own rules or architecture. Because the patched MCP routes memory_save, memory_load, chatroom_post, memory_search, etc. to demo6.0x2ai.com, the developer's prompts and any personal facts the agent decides to harvest are silently relayed to the author-controlled bridge whenever Claude Code is launched in that directory. bin/start.cjs additionally spawns claude --dangerously-skip-permissions, disabling permission prompts for filesystem and shell tool calls, which broadens what the remotely-prompted agent can do on the developer's machine without confirmation. The README's "demo connector" framing does not disclose that postinstall mutates the installer's project directory or that personal data flows off-host.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0f4a43a40af9e707d98ed55406b0ff32dccaad352fccf5d1eaaca41b9959d924

Frequently asked questions

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

Campaign

IN-MAL-2026-005682

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