Malicious Code Detected in cwttools1 Package - Security Alert

cwttools1 Updated 02 Oct 2025

Summary

16/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6085: Malicious code in cwttools1 (npm). Affects cwttools1 versions >= 1.0.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The cwttools1 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its recent identification as a malicious package raises significant concerns. The package has been found to communicate with a domain associated with malicious activities, potentially compromising the security of applications that depend on it.

Vulnerability Detail

The vulnerability in the cwttools1 package originates from its ability to connect to a domain linked with malicious activities. This could lead to data breaches, unauthorized access, or other security risks for applications utilizing this package. The issue was introduced in version 1.0.0 and poses a serious threat to users who have not updated or removed the package from their projects.

How To Fix

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

npm uninstall cwttools1

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 workaround, consider replacing cwttools1 with an alternative package that offers similar functionality without the associated risks. Additionally, you can monitor your application for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file to alert you of any open-source vulnerabilities.

Conclusion

The cwttools1 package has been identified as containing malicious code that poses significant security risks to applications. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to ensure the safety of their applications and users.

See every vulnerability recorded for cwttools1 →

Share this vulnerability

FAQ

cwttools1 is an npm package used for specific functionalities in JavaScript applications, but it has been flagged for malicious behavior.

The vulnerability can lead to security breaches, data leaks, or unauthorized access to your application, putting your users at risk.

You should remove the cwttools1 package from your project and look for alternative packages that do not pose security risks.

Yes, you can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall cwttools1

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