MAL-2026-12182 Malicious code in json-validator-utils (npm)
Malicious package
Published
MAL-2026-12182 is a malicious package: json-validator-utils (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-12182/ (Markdown: https://insights.sbomify.com/MAL-2026-12182/index.md)
- Package
- json-validator-utils
- Registry
- npm
What is MAL-2026-12182?
MAL-2026-12182 is a malicious package in json-validator-utils, published on 5 Aug 2026.
Official description
The package advertises itself as a JSON/XML validator but lib/core.js contains a multi-stage dropper triggered on any call to the public API (validateJson/validateXml). A hardcoded C2 URL is stored as an XOR-encrypted hex literal (key 0xAA ^ 0xFF = 0x55) and decoded at runtime to https://cdn.jsdelivr.net/gh/cryptonomad411/cool-utils/package.json — a personal GitHub account unrelated to the package's stated purpose. The decoded manifest supplies a platform+arch-keyed payload URL that is downloaded to /tmp or %TEMP% and executed (cscript on Windows; chmod+x and spawn('sh',…) on Linux/macOS). Execution is gated behind os.uptime() >= 300 to evade short-lived analysis sandboxes and CI containers. After running the second-stage payload, the Linux branch writes a randomly-named unit to ~/.config/systemd/user and enables it via
systemctl --user enable --now, and the macOS branch writes a randomly-named plist to ~/Library/LaunchAgents and loads it via launchctl load -w, granting persistent auto-start execution of attacker-controlled code on the installer's host.What should I do about MAL-2026-12182?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.