MAL-2026-16095 Malicious code in matrixkit-js (npm)
Malicious package
Published
MAL-2026-16095 is a malicious package: matrixkit-js (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-16095/ (Markdown: https://insights.sbomify.com/MAL-2026-16095/index.md)
- Package
- matrixkit-js
- Registry
- npm
What is MAL-2026-16095?
MAL-2026-16095 is a malicious package in matrixkit-js, published on 9 Sep 2026.
Official description
The package advertises itself as a dense-matrix math library but its main entry matrix.js has been modified post-build to require('./src/init') and invoke initMatrix(…) at module load. src/init.js is an obfuscated single-line string-array loader (112-entry rotated array with numeric-index decoder) that uses crypto (aes-256-gcm, scryptSync, createDecipheriv, setAuthTag), fs, path, and zlib to AES-256-GCM-decrypt a base64-encoded on-disk filename, write the decrypted module to a.tmp file, require() it, and invoke its export with a runtime-supplied password. The sibling files src/statMatrix.min.d.js (~1.15MB base64 decoding to ~862KB of high-entropy bytes), src/statMatrix.min.js (~24KB), and src/utilMatrix.min.d.js (~12KB) are single-string base64 blobs decoding to opaque AES-GCM ciphertext — not JavaScript and absent from matrix.js.map, which lists only the clean rollup output. The loader lines are also absent from the source map, confirming they were injected after the legitimate build. On require()ing the package, the encrypted payload is decrypted and executed as opaque author-controlled code.
What should I do about MAL-2026-16095?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.