Which versions of chief-proxy-out are malicious?

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

How do I remediate chief-proxy-out if I installed it?

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

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

Yes — chief-proxy-out is associated with the GHSA-86cf-7fc5-p98v 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-proxy-out 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-proxy-out (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-proxy-out across your stack and pipelines.

Malicious package

chief-proxy-outnpm

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

MAL-2026-2674

Immediate action

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

npm uninstall chief-proxy-out

What this malware does

The package chief-proxy-out 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)

cc92974c8b9f8dc914e29b747314307d52026764bd99c484f10fad298df29f69

9b408fee03920bbac11e3f3e2a31fa1948a9d1b99041e54c1e10ba0f5e8cf949

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-proxy-out (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-proxy-out across your stack and pipelines.
If you installed it — respond
Remove chief-proxy-out 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-proxy-out 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-proxy-out 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-proxy-out 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-86cf-7fc5-p98v

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks chief-proxy-out-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