Which versions of @supersurkhet/cli are malicious?

The following npm versions of @supersurkhet/cli are flagged malicious: 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7. Treat any of these as compromised.

How do I remediate @supersurkhet/cli if I installed it?

@supersurkhet/cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @supersurkhet/cli — how do I know if it already compromised me?

If @supersurkhet/cli 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 @supersurkhet/cli part of a known attack campaign?

Yes — @supersurkhet/cli is associated with the GHSA-5fx3-327x-w6m7 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 @supersurkhet/cli 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 @supersurkhet/cli (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @supersurkhet/cli across your stack and pipelines.

Malicious package

@supersurkhet/clinpm

Malicious code in @supersurkhet/cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3457

Immediate action

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

npm uninstall @supersurkhet/cli

What this malware does

The package @supersurkhet/cli 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.

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

6 flagged

0.0.20.0.30.0.40.0.50.0.60.0.7

Indicators of compromise (SHA-256)

697bbf316d2671d574ce30298f813c67ed541c6480b6dc1db40e6bb0bf4f6356

dcd203b98b39c0f8bac060d8c7f05221602c714cb29ca6449127b0e09d26adac

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

3219a7aa4b5f19cda44ae4217d0cf1d596988bd05ea1645b489ec579c50bcf17

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @supersurkhet/cli (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @supersurkhet/cli across your stack and pipelines.
If you installed it — respond
@supersurkhet/cli is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @supersurkhet/cli 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 @supersurkhet/cli 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. @supersurkhet/cli on npm has been identified as a malicious package (versions 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5fx3-327x-w6m7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @supersurkhet/cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring