NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

stream-buffer-utils-testmetestnpm

Advisory published Updated

stream-buffer-utils-testmetest is a confirmed malicious npm package (MAL-2026-20280) 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 stream-buffer-utils-testmetest (npm)

MAL-2026-20280
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall stream-buffer-utils-testmetest

What this malware does

On require(), index.js brotli-decompresses a hex-encoded blob and pipes the decoded script into a bun - subprocess, resolving the Bun binary from /usr/local/bin/bun, $HOME/.bun/bin/bun, and $BUN_INSTALL/bin/bun. The payload is shipped as opaque compressed bytes rather than readable source, and executes through a sibling runtime so the code path is not visible to Node-source review of the shipped file. The package advertises itself as a generic utility library, which does not require decoding and executing an embedded blob under an alternate runtime at module load. The current decoded content is a trivial console.log, but the delivery mechanism supports swapping in arbitrary code in any subsequent publish while keeping the Node-level file structurally unchanged. The package name has a placeholder/test shape (stream-buffer-utils-testmetest).

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

3f98853d3cbad88cc14f8d522013ad661d83bee6b5e895ecd48931e498a618ac

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for stream-buffer-utils-testmetest (version 1.0.0).

  2. If you installed it — respond

    Remove stream-buffer-utils-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.

  3. Did it already run?

    If stream-buffer-utils-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

No. stream-buffer-utils-testmetest 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-022920

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks stream-buffer-utils-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.

Explore

stream-buffer-utils-testmetest (npm) malicious package — MAL-2026-20280 | O3 Security