MAL-2026-13963 Malicious code in vexium-kit (npm)
Malicious package
Published
MAL-2026-13963 is a malicious package: vexium-kit (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-13963/ (Markdown: https://insights.sbomify.com/MAL-2026-13963/index.md)
- Package
- vexium-kit
- Registry
- npm
What is MAL-2026-13963?
MAL-2026-13963 is a malicious package in vexium-kit, published on 13 Aug 2026.
Official description
On require, index.js issues an HTTPS request to the hardcoded bare-IP endpoint https://31.97.137.157:45000/icons/116 and passes the response's
credits field to new Function('require','module',...,'Promise', data.credits), executing operator-controlled JavaScript with require, process, and Buffer in scope. The remote-eval sink is named getPlugin, accompanied by an unused setDefaultModule decoy referencing font-awesome CDN paths, while the README advertises the package as a zero-dependency utility toolkit. Declared dependencies (@primno/dpapi, better-sqlite3, sqlite3, node-machine-id) match the toolkit shape used to decrypt Chromium DPAPI-protected cookies/passwords and read browser Login Data databases, indicating the operator-supplied payload's intended follow-on capability against the installer.What should I do about MAL-2026-13963?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.