Critical Malicious Code Vulnerability in @cwlib/core Package

@cwlib/core Updated 02 Oct 2025

Summary

28/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6686: Malicious code in @cwlib/core (npm). Affects @cwlib/core versions >= 30.0.20. 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 @cwlib/core package is a JavaScript library used in Node.js applications, providing core functionalities for developers. It is widely utilized in various projects due to its ease of integration and robust features. However, a recent vulnerability has been identified that compromises its security, allowing it to communicate with a domain associated with malicious activities.

Vulnerability Detail

The vulnerability, identified as MAL-2025-6686, originates from version 30.0.20 of the @cwlib/core package. This issue allows the package to establish connections with a malicious domain, potentially leading to data breaches, unauthorized access, or other malicious actions. The risk is significant as it can affect any application utilizing this package, exposing sensitive information and compromising application integrity.

How To Fix

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

npm uninstall @cwlib/core

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, consider removing the @cwlib/core package from your project until a secure version is available. You can uninstall it using the following command: npm uninstall @cwlib/core.

Conclusion

The @cwlib/core package has a critical vulnerability that allows it to communicate with malicious domains. It is crucial for developers to update to a secure version or remove the package temporarily to protect their applications. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for @cwlib/core →

Share this vulnerability

FAQ

The vulnerability allows the package to communicate with a domain linked to malicious activities, posing security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

As a temporary measure, consider uninstalling the package until a secure version is released.

Ensure to update to the latest version of @cwlib/core that addresses the vulnerability. Check the package repository for details.

Vulert uses your package-lock.json file to monitor and alert you in real-time about open-source vulnerabilities, ensuring your application remains secure.

How To Fix

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

npm uninstall @cwlib/core

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