Which versions of shakti20261 are malicious?

The following npm versions of shakti20261 are flagged malicious: 1.0.0, 3.0.0. Treat any of these as compromised.

How do I remediate shakti20261 if I installed it?

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

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

Yes — shakti20261 is associated with the GHSA-357m-gr33-h5ww 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 shakti20261 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 shakti20261 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging shakti20261 across your stack and pipelines.

Malicious package

shakti20261npm

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

MAL-2025-192677

Immediate action

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

npm uninstall shakti20261

What this malware does

The package shakti20261 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.

The OpenSSF Package Analysis project identified 'shakti20261' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

1.0.03.0.0

Indicators of compromise (SHA-256)

094704394ab9df6c436ad0e222252c918d380bcdd0481bd94621d484e60c7d42

e0f08e815a821119f6e2060f763b8e017961c5fd745efe39bae1c278f7358987

a217c3c91ff80edbc760c82358d7d22c5819f0110ccf221e4d3639eb22e08ac7

e75357912e9e470657d646a2fd23a82c2f23cd2a6d0a987fb5b880eb8fa4c731

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

Campaign

GHSA-357m-gr33-h5ww

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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