MAL-2026-17317 Malicious code in booking-tasks (npm)
Malicious package
Published
MAL-2026-17317 is a malicious package: booking-tasks (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-17317/ (Markdown: https://insights.sbomify.com/MAL-2026-17317/index.md)
- Package
- booking-tasks
- Registry
- npm
What is MAL-2026-17317?
MAL-2026-17317 is a malicious package in booking-tasks, published on 30 Sep 2026.
Official description
The package's package.json declares a postinstall hook
wscript.exe 4444.vbs that fires automatically on npm install. The bundled 4444.vbs contains hand-rolled AES-128 (with XOR-masked forward/inverse S-boxes), a ChaCha20-IETF stream, XOR-masked SHA-256 round constants, a Base64 decoder via MSXML DOM, and a chunked Base64 ciphertext blob (ArtifactBundleHX, ~665 chunks). At install time the VBScript decrypts these chunks into a PowerShell loader, writes it to %TEMP%\pf<rand>.dat, and hands it to powershell.exe for process hollowing, giving the publisher arbitrary code execution on the installer's Windows host. The shipped library surface (src/index.js) is a small Zod-validated checkEligibility() function that never references 4444.vbs, and readme.md states 'No network requests. No personal data storage. No installation scripts.' — a direct contradiction of the declared postinstall hook, indicating the source module is a decoy for the dropper. The multi-primitive crypto and chunked-Base64 encoding of the payload serve only to hide executable content from static inspection.What should I do about MAL-2026-17317?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.