Which versions of victim-package-b are malicious?

The following npm versions of victim-package-b are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate victim-package-b if I installed it?

Remove victim-package-b 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.

I already installed victim-package-b — how do I know if it already compromised me?

If victim-package-b 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 victim-package-b part of a known attack campaign?

Yes — victim-package-b is associated with the GHSA-v876-w8f6-cgvx, RLMA-2026-01639 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 victim-package-b 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 victim-package-b (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging victim-package-b across your stack and pipelines.

Malicious package

victim-package-bnpm

Malicious code in victim-package-b (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-400

Immediate action

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

npm uninstall victim-package-b

What this malware does

The package victim-package-b was found to contain malicious code.

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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

324aadc54f696916c968e82f4704d088384eab1ce76c08f2a3d3d0aa59fece7d

152e8188fd82f0ea4ee410d725bb96ab33af5767241fcefb555ef8dfaffd39bf

528e27afe4be6335226d238767fbe28f1fa8ee6f2d0586b52751032ad4926d59

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for victim-package-b (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging victim-package-b across your stack and pipelines.
If you installed it — respond
Remove victim-package-b 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.
Did it already run?
If victim-package-b 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 victim-package-b 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. victim-package-b on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v876-w8f6-cgvxRLMA-2026-01639

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks victim-package-b-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.

Malware detection Runtime egress monitoring