Critical Malicious Code Vulnerability in spamsms Package

spamsms Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192671: Malicious code in spamsms (npm). Affected versions are not published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The spamsms package is an npm library designed for sending spam SMS messages. It is often used in various applications that require SMS functionalities. However, this package has been compromised, embedding malicious code that can lead to severe security breaches. Users of this package should be aware of its potential risks and the implications of its use.

Vulnerability Detail

The vulnerability originates from the spamsms package, which has been identified as containing malicious code. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code. The ramifications of this vulnerability are significant, as it can lead to complete control of the affected system by an outside entity.

How To Fix

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

npm uninstall spamsms

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that all sensitive information is rotated and that your environment is scanned for any remaining malicious software.

Conclusion

The spamsms package has been identified as a critical security risk due to embedded malicious code. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for spamsms →

Share this vulnerability

FAQ

The spamsms package is an npm library used for sending spam SMS messages, but it has been compromised with malicious code.

If you have the spamsms package installed, your system is likely compromised. It is advisable to remove the package immediately.

You should rotate all secrets and keys from a different, secure computer to prevent unauthorized access.

No, there is currently no patched version available for the spamsms package. The only solution is to remove it.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall spamsms

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