Which versions of buffer-wrap-67d7 are malicious?

The following npm versions of buffer-wrap-67d7 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate buffer-wrap-67d7 if I installed it?

buffer-wrap-67d7 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 buffer-wrap-67d7 — how do I know if it already compromised me?

If buffer-wrap-67d7 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 buffer-wrap-67d7 part of a known attack campaign?

Yes — buffer-wrap-67d7 is associated with the IN-MAL-2026-007373 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 buffer-wrap-67d7 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 buffer-wrap-67d7 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging buffer-wrap-67d7 across your stack and pipelines.

Malicious package

buffer-wrap-67d7npm

Malicious code in buffer-wrap-67d7 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6348

Immediate action

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

npm uninstall buffer-wrap-67d7

What this malware does

The package declares a postinstall hook ("postinstall": "node run.js") that executes run.js automatically on npm install. run.js imports os, fs, http, https, and child_process, and collects host and user identity signals including os.hostname(), os.userInfo(), os.platform(), process.env.USER, and process.cwd(), alongside filesystem reads (fs.existsSync, fs.readFileSync). Collected data is base64-encoded (Buffer.from(...).toString('base64')) and POSTed out via http/https calls (multiple POST sites at run.js lines 131, 339, 346). The composition — automatic lifecycle trigger, system/user reconnaissance, base64 packaging, and outbound POSTs — is the canonical install-time exfiltration shape and produces direct attacker benefit (host fingerprinting and credential-adjacent data leaving the installer's machine).

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a0192c1f2bf35c50a401e2df63f505564880339f5329c0ffcfdb8748cd6d48e3

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 buffer-wrap-67d7 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging buffer-wrap-67d7 across your stack and pipelines.
If you installed it — respond
buffer-wrap-67d7 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 buffer-wrap-67d7 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-wrap-67d7 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. buffer-wrap-67d7 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-007373

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks buffer-wrap-67d7-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