Which versions of chief-documentation are malicious?

Every published version of chief-documentation on npm is considered malicious. Remove the package entirely.

How do I remediate chief-documentation if I installed it?

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

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

Yes — chief-documentation is associated with the GHSA-8r2m-gvh8-jfqm 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 chief-documentation 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 chief-documentation (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging chief-documentation across your stack and pipelines.

Malicious package

chief-documentationnpm

Malicious code in chief-documentation (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2673

Immediate action

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

npm uninstall chief-documentation

What this malware does

The package chief-documentation 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

2e36a61facc3d4e38e9b26d8898a969cf072181b0fb36b3db56b56a990f91bf5

4685fab18e6de4de4fba0c842db2c4ee4114ca7259b8339900078fec02724a39

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

Campaign

GHSA-8r2m-gvh8-jfqm

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chief-documentation-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