buffer-utilitiesnpm
Malicious code in buffer-utilities (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
buffer-utilities impersonates the legitimate buffer package by Feross Aboukhadijeh, copying its name, email, homepage, and GitHub repo metadata, and advertises itself as 'Node.js Buffer API, for the browser'. At require() time, index.js (lines 43-52) executes an IIFE that base64-decodes the string aHR0cHM6Ly93d3cuanNvbmtlZXBlci5jb20vYi9DV09WOQ== to https://www.jsonkeeper.com/b/CWOV9, performs an HTTP fetch, and passes the response's data.content field directly to eval(). jsonkeeper.com is a mutable anonymous JSON paste host: whoever controls the paste can change the executed payload at any time, with no version bump or republication of the package. Any application that imports buffer-utilities — including by accidental name confusion against the popular buffer package — runs whatever JavaScript the paste currently returns, with full process privileges. The base64-encoded URL constant is a deliberate obfuscation to defeat static URL scanning.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The OpenSSF Package Analysis project identified 'buffer-utilities' @ 1.0.0 (npm) as malicious.
It is considered malicious because:
-
The package communicates with a domain associated with malicious activity.
-
The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for buffer-utilities (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging buffer-utilities across your stack and pipelines.
If you installed it — respond
buffer-utilities is a typosquat — you almost certainly intended a legitimately-named package. Remove buffer-utilities, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If buffer-utilities was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks buffer-utilities before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks buffer-utilities-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.