Which versions of cxpher-linux-arm32 are malicious?

The following npm versions of cxpher-linux-arm32 are flagged malicious: 2.0.22. Treat any of these as compromised.

How do I remediate cxpher-linux-arm32 if I installed it?

Remove cxpher-linux-arm32 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 cxpher-linux-arm32 — how do I know if it already compromised me?

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

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

Malicious package

cxpher-linux-arm32npm

Malicious code in cxpher-linux-arm32 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4547

Immediate action

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

npm uninstall cxpher-linux-arm32

What this malware does

The package's main is an ARM ELF binary that, when loaded, mkdtemp's a working directory under /dev/shm/.cxpher.XXXXXX or /tmp/.cxpher.XXXXXX, writes an unpacked JavaScript file (a.js and /tmp/.cxpher-wrap.%d.js), locates node at /usr/local/bin/node or /usr/bin/node, and execvp's node against the unpacked file. The bytes that ultimately run are decoded from an opaque high-entropy blob inside the ELF and are not human-auditable from the published tarball — equivalent to eval(decode(blob)) but in native form. The same binary reads /proc/self/status and parses the TracerPid: field, the canonical Linux anti-ptrace anti-debug check; legitimate native addons do not need this. Package metadata is placeholder (no author, homepage, repository, or README; description is the generic string "Native binary for cxpher on linux-arm32"), and the binary references an alternate environment-variable prefix (AGPK_AUDIO_FD alongside CXPHER_AUDIO_FD) suggesting it was renamed/repurposed from a different project. No documentation describes what code is unpacked and run on the installer's machine.

Malicious versions

1 flagged

2.0.22

Indicators of compromise (SHA-256)

cd6c14d2899b638880b25bf1c35973ed1c9cf6fcb99331447e3da7c2478124c7

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

Campaign

IN-MAL-2026-004526

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cxpher-linux-arm32-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