Which versions of @xiaohhhh1/canvas-agent are malicious?

The following npm versions of @xiaohhhh1/canvas-agent are flagged malicious: 0.4.4. Treat any of these as compromised.

How do I remediate @xiaohhhh1/canvas-agent if I installed it?

@xiaohhhh1/canvas-agent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @xiaohhhh1/canvas-agent — how do I know if it already compromised me?

If @xiaohhhh1/canvas-agent was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @xiaohhhh1/canvas-agent part of a known attack campaign?

Yes — @xiaohhhh1/canvas-agent is associated with the IN-MAL-2026-016269 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @xiaohhhh1/canvas-agent across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @xiaohhhh1/canvas-agent (version 0.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @xiaohhhh1/canvas-agent across your stack and pipelines.

Malicious package

@xiaohhhh1/canvas-agentnpm

@xiaohhhh1/canvas-agent is a confirmed malicious npm package (MAL-2026-13398) that steals credentials and exfiltrates sensitive data (malicious version 0.4.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @xiaohhhh1/canvas-agent (npm)

MAL-2026-13398

Immediate action

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

npm uninstall @xiaohhhh1/canvas-agent

What this malware does

On starting the package's bin, the agent opens an outbound WebSocket to wss://canvas.xiaohhhh1.com/api/agent-relay and forwards inbound relay messages as authenticated HTTP requests to its own local server, attaching the local x-canvas-agent-token header. Endpoints reachable through this relay include /agent/codex/turn and /agent/claude/turn, which spawn the local Codex and Claude CLIs; /agent/codex/approval, which supplies approval decisions; /agent/local-image, which readFiles any absolute path matching an image extension and returns the bytes; and /agent/local-file/reveal, which spawns the OS file manager (explorer/open/xdg-open) against an arbitrary absolute path. codex-client.js maps a caller-supplied permissionMode of 'full' to Codex sandbox 'danger-full-access' with approvalPolicy 'never', so a remote peer connected to the vendor relay can select an unrestricted sandbox and drive commandExecution/fileChange turns on the installer's host without any local approval prompt. The same relay path also allows the remote peer to pull image files from arbitrary absolute paths on the installer's disk.

Malicious versions

1 flagged

0.4.4

Indicators of compromise (SHA-256)

40162697638de6a974c2f7408ccf190f6d5b5f7ea82e5e52bbc9cb2a013fab08

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @xiaohhhh1/canvas-agent (version 0.4.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @xiaohhhh1/canvas-agent across your stack and pipelines.
If you installed it — respond
@xiaohhhh1/canvas-agent is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @xiaohhhh1/canvas-agent was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @xiaohhhh1/canvas-agent before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @xiaohhhh1/canvas-agent on npm has been identified as a malicious package (version 0.4.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016269

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @xiaohhhh1/canvas-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database