event-bus-lite-testmetestnpm
Advisory published Updated
event-bus-lite-testmetest is a confirmed malicious npm package (MAL-2026-18292) that executes malicious code on install (malicious version 0.0.6). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in event-bus-lite-testmetest (npm)
What this malware does
The package ships a binding.gyp whose target has type "none" and no C/C++ source files; its only purpose is a GYP <!(...) command-expansion that runs node index.js during the automatic node-gyp rebuild triggered by npm install. index.js is multi-layer obfuscated: a char-code array is Caesar-decoded (shift 21) and passed to eval; the decoded body reads the bundled lib_native.dat (~312 KB, high-entropy, sha256 e1ab1e330d3db532d511d4af4386ab2d2c6245ca807410f51c1211ae48814d73), brotli-decompresses and AES-128-GCM-decrypts it with hardcoded key/IV/AAD, writes the plaintext to a mkdtempSync('.b-')/index.js temp path, and spawns the Bun runtime (Bun.spawn, or getBunPath() via child_process.spawn) to execute the decrypted payload. Executing under Bun bypasses Node-only analysis. The contents of the executed payload are not inspectable from the shipped artifact.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for event-bus-lite-testmetest (version 0.0.6).
If you installed it — respond
Remove event-bus-lite-testmetest 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 event-bus-lite-testmetest 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks event-bus-lite-testmetest-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.