npm

The event-bus-lite-testmetest npm Supply Chain Attack

Updated 16 Nov 2026 · Incident date 22 Oct 2026

event-bus-lite-testmetest 0.0.6 on npm decrypted a bundled file at install time and ran the result with the Bun runtime, according to GitHub and OpenSSF.

GitHub advisory GHSA-7xwf-5j6m-rjff and OpenSSF record MAL-2026-18292 class version 0.0.6 as malware. Both come from one Amazon Inspector report.

What happened

The advisory describes an install-time loader in version 0.0.6.

  • A binding.gyp file runs node index.js during the automatic node-gyp rebuild.
  • index.js decodes a character-code array with a Caesar shift of 21 and passes it to eval.
  • The decoded code decompresses and decrypts the bundled lib_native.dat with AES-128-GCM.
  • It writes the result to a .b- temp folder and runs it with Bun.

The package code was unavailable for inspection. The advisory says nobody can inspect the final program from the package.

Affected versions

  • 0.0.6. GitHub and OpenSSF name this version only.
  • npm lists 1,376 downloads, all on 22 October 2026. The count does not separate people from mirrors.

Indicators of compromise

  • binding.gyp sha256 174b6c9e614ba57ddd1e4ef2dd8207629617d4329ed6991e42e393b1f96dfada
  • index.js sha256 d0d4ab44881f4392637ca23026579b51e7fc7d01fbae9ead5c74cef96c71e016
  • lib_native.dat sha256 e1ab1e330d3db532d511d4af4386ab2d2c6245ca807410f51c1211ae48814d73
  • event-bus-lite-testmetest-0.0.6.tgz sha1 b7c2cf96a04b0d130ab7913ee5fdd9defd1dd125

How to check

Run this command in each project folder. It only reads the dependency tree.

npm ls event-bus-lite-testmetest

Search your npm cache for the name.

grep -rl "event-bus-lite-testmetest" ~/.npm/_cacache/index-v5

What to do now

  1. Remove the package from package.json and the lockfile.
  2. Delete node_modules and any .b- temp folder.
  3. If a computer installed 0.0.6, treat it as compromised, as GitHub advises.
  4. From a different computer, rotate every secret and key that the affected computer held.

What Vigilance would show

Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.

On the computer, at install

Vigilance blocked `event-bus-lite-testmetest` 0.0.6. This version is too new or changed in a way Vigilance must check first.

In the owner report

Bad update

event-bus-lite-testmetest 0.0.6

This update now downloads from the internet. The version before it did not.

Frequently asked questions

Which version of event-bus-lite-testmetest is malicious?

GitHub and OpenSSF name version 0.0.6 only.

What does the hidden program do?

No source says. The program stays encrypted inside the package.

Sources

  1. github.com/advisories/GHSA-7xwf-5j6m-rjff
  2. raw.githubusercontent.com/ossf/malicious-packages/main/osv/malicious/npm/event-bus-lite-testmetest/MAL-2026-18292.json
  3. api.npmjs.org/downloads/range/2026-01-01:2026-11-15/event-bus-lite-testmetest

More supply chain attacks

All 145 attacks in the library · npm supply chain attacks · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library