Malicious Code Detected in shakti-strings Package - Version 1.4.0

shakti-strings Updated 20 Mar 2026

Summary

20/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2003: Malicious code in shakti-strings (npm). Affects shakti-strings versions 1.4.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The shakti-strings package is an npm library designed for string manipulation and processing in JavaScript applications. It provides various utilities for handling strings efficiently. However, version 1.4.0 of this package has been flagged for containing malicious code that communicates with a domain linked to harmful activities, posing a security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the shakti-strings package arises from its malicious behavior, specifically its communication with a domain associated with malicious activities. This could lead to data exfiltration, unauthorized access, or other security breaches within applications that depend on this package. The OpenSSF Package Analysis project identified this issue, marking the package as malicious due to its potential to compromise application integrity.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall shakti-strings

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can avoid using the shakti-strings package altogether and seek alternative libraries that provide similar functionality without the associated risks. Additionally, ensure that your application is monitored for any suspicious activity.

Conclusion

The shakti-strings package version 1.4.0 has been identified as malicious due to its communication with a harmful domain. It is crucial for developers to update or replace this package to protect their applications from potential security threats. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for shakti-strings →

Share this vulnerability

FAQ

shakti-strings is an npm package used for string manipulation in JavaScript applications.

Version 1.4.0 is flagged as malicious because it communicates with a domain linked to harmful activities.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

You should uninstall the affected version and install a secure alternative or the latest version of the package.

Yes, there are several other libraries available for string manipulation in JavaScript, such as lodash or string.js, which do not have known vulnerabilities.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall shakti-strings

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback