Which versions of booking-eligibility are malicious?

The following npm versions of booking-eligibility are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate booking-eligibility if I installed it?

Remove booking-eligibility from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed booking-eligibility — how do I know if it already compromised me?

If booking-eligibility was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is booking-eligibility part of a known attack campaign?

Yes — booking-eligibility is associated with the IN-MAL-2026-020799 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find booking-eligibility across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for booking-eligibility (version 1.0.0).

Malicious package

booking-eligibilitynpm

Advisory published Sep 30, 2026Updated Sep 30, 2026

booking-eligibility is a confirmed malicious npm package (MAL-2026-17316) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in booking-eligibility (npm)

MAL-2026-17316

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall booking-eligibility

What this malware does

package.json declares a postinstall lifecycle hook wscript.exe 4444.vbs that runs Windows Script Host against a .vbs file on npm install. The referenced 4444.vbs is not shipped in the tarball, so the hook either fails or (if the file is dropped by another mechanism or provided out-of-band) executes attacker-authored VBScript on the installer's machine at install time. The README explicitly claims 'No installation scripts', directly contradicting the manifest — a cover-story mismatch that misrepresents install-time behavior. The 4444 filename mirrors a well-known reverse-shell port convention. The package presents no legitimate functionality justifying WSH execution at install time.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2c93f5b06720659d8e0cc8efb7d6bd75f577605e84c27cfb600a795081c27654

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for booking-eligibility (version 1.0.0).
If you installed it — respond
Remove booking-eligibility from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If booking-eligibility was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. booking-eligibility on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020799

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks booking-eligibility-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database