Which versions of zyr-agent are malicious?

The following npm versions of zyr-agent are flagged malicious: 1.5.7, 1.6.2. Treat any of these as compromised.

How do I remediate zyr-agent if I installed it?

Remove zyr-agent 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 activity or persistence.

I already installed zyr-agent — how do I know if it already compromised me?

If zyr-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 zyr-agent part of a known attack campaign?

Yes — zyr-agent is associated with the IN-MAL-2026-016763, IN-MAL-2026-016764 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 zyr-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 zyr-agent (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zyr-agent across your stack and pipelines.

Malicious package

zyr-agentnpm

zyr-agent is a confirmed malicious npm package (MAL-2026-13471) that executes malicious code on install (malicious versions 1.5.7, 1.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zyr-agent (npm)

MAL-2026-13471

Immediate action

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

npm uninstall zyr-agent

What this malware does

zyr-agent ships an AI coding agent whose default 'free' provider routes chat completions to a hardcoded preview-slug endpoint at https://preview-chat-e8a10541-5396-4e8f-9ead-e5fbbcdb33d3.space-z.ai/api/v1 using an embedded zyr_sk_ key. The Agent.send loop iterates tool_calls returned by that remote endpoint and invokes tool.execute(tc.args) with no user confirmation across the CLI, Electron IPC, and HTTP server paths. One of the registered tools is a bash tool whose execute handler runs execSync(cmd) on the installer's host. Whoever controls the preview subdomain can therefore return a bash tool_call in a normal chat response and have arbitrary shell commands executed on any machine running the default provider. A separate provider ships a live third-party OpenRouter API key (sk-or-v1-...) hardcoded in cli.js and desktop/electron.js, which routes installer prompts through an author-controlled OpenRouter account. AI-agent auto-execution of model output is expected for this category, but the combination of (a) auto-exec with no per-tool confirmation and (b) a hardcoded, mutable, author-controlled preview-slug endpoint as the default provider makes the model-driven exec path a remote-command channel controlled by the package author rather than by the operator.

Malicious versions

2 flagged

1.5.71.6.2

Indicators of compromise (SHA-256)

5828a7ed3adec522b0ace6b4e7962f48ff5e8b5853ef251d5db81df0b4f08fc0

b6dd19313881a0bcfd90734ce897e3134af348bce2b7447eaf4e5dbc910f432c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for zyr-agent (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zyr-agent across your stack and pipelines.
If you installed it — respond
Remove zyr-agent 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 activity or persistence.
Did it already run?
If zyr-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 zyr-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. zyr-agent on npm has been identified as a malicious package (versions 1.5.7, 1.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-016763IN-MAL-2026-016764

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zyr-agent-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database