MAL-2026-4547 Malicious code in cxpher-linux-arm32 (npm)
Malicious package
Published
MAL-2026-4547 is a malicious package: cxpher-linux-arm32 (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4547/ (Markdown: https://insights.sbomify.com/MAL-2026-4547/index.md)
- Package
- cxpher-linux-arm32
- Registry
- npm
What is MAL-2026-4547?
MAL-2026-4547 is a malicious package in cxpher-linux-arm32, published on 24 May 2026.
Official description
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.What should I do about MAL-2026-4547?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.