Which versions of shakti-strings are malicious?

The following npm versions of shakti-strings are flagged malicious: 1.4.0. Treat any of these as compromised.

How do I remediate shakti-strings if I installed it?

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

If shakti-strings was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find shakti-strings across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shakti-strings (version 1.4.0).

Malicious package

shakti-stringsnpm

Advisory published Mar 20, 2026Updated Mar 23, 2026

shakti-strings is a confirmed malicious npm package (MAL-2026-2003) that executes malicious code on install (malicious version 1.4.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shakti-strings (npm)

MAL-2026-2003

Immediate action

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

npm uninstall shakti-strings

What this malware does

The package shakti-strings was found to contain malicious code.

The OpenSSF Package Analysis project identified 'shakti-strings' @ 1.4.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.4.0

Indicators of compromise (SHA-256)

aa19f1d5261846b18a1a4f35020c31393119768f0856d30d87677c06fd680fe5

7f2263a09a764a00c111f0baad35ef067d15ac1baaf92efd30cf27d86a4adc66

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for shakti-strings (version 1.4.0).
If you installed it — respond
Remove shakti-strings 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 shakti-strings was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. shakti-strings on npm has been identified as a malicious package (version 1.4.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks shakti-strings-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

Explore

All malware advisories How O3 detects malware Vulnerability database