Which versions of pcl-build-docroot are malicious?

The following npm versions of pcl-build-docroot are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate pcl-build-docroot if I installed it?

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

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

Yes — pcl-build-docroot is associated with the GHSA-9fgh-86m3-xx7g, RLMA-2026-01480, RLUA-2026-01805 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 pcl-build-docroot 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 pcl-build-docroot (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 pcl-build-docroot across your stack and pipelines.

Malicious package

pcl-build-docrootnpm

Malicious code in pcl-build-docroot (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1361

Immediate action

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

npm uninstall pcl-build-docroot

What this malware does

The package pcl-build-docroot 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)

6a908bc33ac530331fc697343b244df6d6a21fb4aca1f23d8e1657464afe30f4

b9f0a78b787880617ea3d46a8d7815e8f3cf32ab3685f8f8e907e463259cee12

ec644efff0c2f83a615a174be4d854af6d4411fec2fd2246ce43b6118f6065fd

0c27941f3547d3bdca8bcf2fb302ffb91b32560fc05b8358c02e703f1b3b20a7

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 pcl-build-docroot (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 pcl-build-docroot across your stack and pipelines.
If you installed it — respond
Remove pcl-build-docroot 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 pcl-build-docroot 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 pcl-build-docroot 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. pcl-build-docroot 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-9fgh-86m3-xx7gRLMA-2026-01480RLUA-2026-01805

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pcl-build-docroot-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