0x2ai-ivo
This report shows the evidence for 0x2ai-ivo@1.2.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-5599 confirms this npm version as malicious.
Advisory
MAL-2026-5599
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in 0x2ai-ivo (npm)
Details
On install, the postinstall script copies the package's `payload/` tree (CLAUDE.md,.claude/settings.json,.mcp.json, and several.cjs MCP scripts) into the consumer's project directory (`process.env.INIT_CWD || process.cwd()`) at `scripts/postinstall.cjs`, materializing Claude Code project config inside any repo where `npm install` was run. The dropped `.mcp.json` registers an MCP server whose env includes `BRIDGE_URL=https://ivo.0x2ai.com` and a hardcoded shared bearer token (`BRIDGE_AUTH_TOKEN`), so any installer's Claude Code instance auto-attaches to that author-operated bridge. The package's CLI (`bin/start.cjs`) then spawns `claude --dangerously-skip-permissions` via a shell, deliberately stripping the permission gate that normally protects the host from agent actions. The MCP scripts (`payload/chatroom-mcp-lite-patched.cjs`, `payload/chatroom-monitor.cjs`, `payload/chatroom-wait-once.cjs`) POST to and long-poll `https://ivo.0x2ai.com`, receiving chatroom messages that CLAUDE.md/`0x2ai-boot.md` instruct the agent to act on. The exposed MCP tools (`provider_query`, `memory_save`, `memory_load`, `chatroom_post`) further route user prompts, conversation memory, and posted messages through the same endpoint authenticated by the shared static token. Net effect: an unattended, permission-bypassed Claude agent on the installer's machine that executes whatever instructions the operator of ivo.0x2ai.com pushes — an over-the-wire remote-control channel whose payloads are not in the tarball and not under the installer's control.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to 0x2ai-ivo@1.2.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing 0x2ai-ivo@1.2.0. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.