Which versions of @oliviamcdaniel12/safer-buffer are malicious?

The following npm versions of @oliviamcdaniel12/safer-buffer are flagged malicious: 2.2.0, 2.2.1. Treat any of these as compromised.

How do I remediate @oliviamcdaniel12/safer-buffer if I installed it?

@oliviamcdaniel12/safer-buffer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @oliviamcdaniel12/safer-buffer — how do I know if it already compromised me?

If @oliviamcdaniel12/safer-buffer 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.

Is @oliviamcdaniel12/safer-buffer part of a known attack campaign?

Yes — @oliviamcdaniel12/safer-buffer is associated with the IN-MAL-2026-010252, IN-MAL-2026-010253, GHSA-88h2-qq8c-r5pv campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @oliviamcdaniel12/safer-buffer across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @oliviamcdaniel12/safer-buffer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @oliviamcdaniel12/safer-buffer across your stack and pipelines.

Malicious package

@oliviamcdaniel12/safer-buffernpm

@oliviamcdaniel12/safer-buffer is a confirmed malicious npm package (MAL-2026-10442) that steals credentials and exfiltrates sensitive data (malicious versions 2.2.0, 2.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @oliviamcdaniel12/safer-buffer (npm)

MAL-2026-10442

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @oliviamcdaniel12/safer-buffer

What this malware does

Package impersonates the popular safer-buffer module. On require(), safer.js reads a PID from Porting-Buffer.md and, if that process is not alive, spawns node tests/safer-buffer.min.js as a detached, hidden, stdio-ignored child, writing the new PID back to the markdown file as a persistence marker. The spawned tests/safer-buffer.min.js is a heavily obfuscated (obfuscator.io-style string-array + control-flow) payload that: (1) connects to Sepolia via Infura (sepolia.infura.io/v3/dc7257d09fab42eca2c354c32fec1938) and Alchemy (eth-sepolia.g.alchemy.com/v2/D2-TbkB2m05WhSnSDOCDI), calls getters (getSPubKey, getCwPrivatePublic, getTData1, getTData2, getLastActiveCwAddress, getChunk, getMetadata) on contract 0x9E4dF8F253Eb439dd9538Fda30cC03B38fD3a631, ECDH+AES-GCM decrypts the retrieved bytes, and spawns them as further node child processes (on-chain dead-drop RCE); (2) gathers host reconnaissance (os.platform, release, arch, hostname, cpu count, total/free memory, uptime) and POSTs it to slack.com/api/chat.postMessage (channel C0ATC9UKKA4) with an embedded xoxb-... bot token, and to api.telegram.org/bot<token>/sendMessage (chat_id -1004326194624); (3) performs anti-forensics — unlinks its own file, safer-test.min.js, safer.min.js, erases the LICENSE, and issues taskkill /PID <pid> /T /F on Windows or process.kill(pid, 'SIGTERM') on POSIX against the prior stored PID, then process.exit(1). The package name lookalike, the on-require detached spawn, the blockchain-based C2, the hardcoded exfiltration endpoints, and the self-deletion together constitute a supply-chain attack against installers.

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.

Malicious versions

2 flagged

2.2.02.2.1

Indicators of compromise (SHA-256)

55129478b44191f3a4bb3308036567d5e2eb1a73084511b424917b6b5f7bf50f

cf89426574c7ad26fbfd2e1fe79108ea4a5bc949069c5f3a9188c4de8c60e2df

6febb5641879a5d3bfa080e1bd2b870310c7bafb2ea2216b114a398306a30775

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @oliviamcdaniel12/safer-buffer (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @oliviamcdaniel12/safer-buffer across your stack and pipelines.
If you installed it — respond
@oliviamcdaniel12/safer-buffer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @oliviamcdaniel12/safer-buffer 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 @oliviamcdaniel12/safer-buffer 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

No. @oliviamcdaniel12/safer-buffer on npm has been identified as a malicious package (versions 2.2.0, 2.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010252IN-MAL-2026-010253GHSA-88h2-qq8c-r5pv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @oliviamcdaniel12/safer-buffer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database