Which versions of unibody are malicious?

The following npm versions of unibody are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate unibody if I installed it?

Remove unibody 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 unibody — how do I know if it already compromised me?

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

Yes — unibody is associated with the GHSA-v8gw-679q-2rc3, RLMA-2026-01633, RLUA-2026-01828 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 unibody 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 unibody (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unibody across your stack and pipelines.

Malicious package

unibodynpm

Malicious code in unibody (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1365

Immediate action

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

npm uninstall unibody

What this malware does

The package unibody 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

99.9.9

Indicators of compromise (SHA-256)

d5083ea858a18dda094f7d171b57730132d8348f914ae8b2895725447d8f13f0

a609cf8d0abc22e4a406c63c074161b8cb27a5dd09116da38c381a48749868ef

62433a668da6675dffc03d0b406316c3a612058aed5063d864c1f6a78d94e937

7fda3e3a4f8ee6db23f57a618063e98de812bd19c02d884c46424725b7cf58a8

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 unibody (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unibody across your stack and pipelines.
If you installed it — respond
Remove unibody 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 unibody 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 unibody 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. unibody on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v8gw-679q-2rc3RLMA-2026-01633RLUA-2026-01828

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks unibody-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