MAL-2026-20280: Malicious code in stream-buffer-utils-testmetest (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (3f98853d3cbad88cc14f8d522013ad661d83bee6b5e895ecd48931e498a618ac) 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 $BUNINSTALL/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).
Affected Software
Event History
Frequently Asked Questions
What conditions are required for the embedded payload to run?
The package's index.js triggers the behavior when it is loaded with require(). It attempts to locate Bun at /usr/local/bin/bun, $HOME/.bun/bin/bun, or $BUN_INSTALL/bin/bun and pipes the decoded payload to a bun - subprocess.
Which environments are most exposed?
Projects that install and require this package on systems where Bun is available in one of the searched locations are exposed to the subprocess execution path. The package presents itself as a generic utility library, so this behavior may be unexpected during dependency review.
Does the currently decoded payload perform harmful actions?
The currently decoded content is described as a trivial console.log. However, the opaque compressed payload can be replaced with arbitrary code in a later publish without changing the visible Node-level structure of index.js.
How can I identify whether this package is present in an application?
Check installed npm dependencies for stream-buffer-utils-testmetest and review whether application code or dependencies load it with require(). The referenced package release is version 1.0.0.