Which versions of chainix are malicious?

The following npm versions of chainix are flagged malicious: 4.4.5. Treat any of these as compromised.

How do I remediate chainix if I installed it?

chainix establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed chainix — how do I know if it already compromised me?

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

Yes — chainix is associated with the IN-MAL-2026-004919, GHSA-mrx8-p3w9-5cfm 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 chainix 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 chainix (version 4.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chainix across your stack and pipelines.

Malicious package

chainixnpm

Malicious code in chainix (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4817

Immediate action

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

npm uninstall chainix

What this malware does

Package presents itself as a pino-compatible logger (README badges link to pinojs/pino, exports alias module.exports.pino = middleware) but its exported middleware spawns a detached node lib/initializeCaller.js. That script base64-decodes a hardcoded URL to https://aqua-margit-84.tiiny.site/index.json, fetches the JSON over HTTPS with a base64-obfuscated x-secret-key header, takes the data.cookie field, and executes it via new Function.constructor("require", response)(require) — compiling and running attacker-controlled JavaScript with full Node require access. The fetch retries 5 times. The C2 URL and header name/value are stored as base64 in a fake process object to evade plain-text scanning. tiiny.site is an anonymous static-hosting service; the content at that URL is mutable and attacker-controlled. This is a remote-code-execution dropper that fires when a consumer application invokes the advertised middleware, giving the attacker arbitrary code execution on any host running the application.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

4.4.5

Indicators of compromise (SHA-256)

93d9609d2eac0c0ff33aed557171138930255798aa649fa648b04814c8cb1908

638ca4910fffe31e7bbaba4da2f69b9df27baff5c1b848415691b5c0aeeec4b4

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for chainix (version 4.4.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chainix across your stack and pipelines.
If you installed it — respond
chainix establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If chainix 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 chainix 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. chainix on npm has been identified as a malicious package (version 4.4.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004919GHSA-mrx8-p3w9-5cfm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chainix-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring