Critical Malicious Code Vulnerability in testpkgcwlib (npm)

testpkgcwlib Updated 02 Oct 2025

Summary

28/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6767: Malicious code in testpkgcwlib (npm). Affects testpkgcwlib versions >= 5.0.2. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'testpkgcwlib' is an npm library designed for developers to facilitate certain functionalities in their applications. It is widely used due to its ease of integration and robust features. However, it has been identified to communicate with a domain associated with malicious activity, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability arises from the package's ability to connect to a malicious domain, which can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. This issue was introduced in version 5.0.2 of the package, making it critical for users to be aware of the risks involved in using this version or any subsequent versions that do not address the issue.

How To Fix

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

npm uninstall testpkgcwlib

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 measure, you can avoid using the affected version of 'testpkgcwlib' by downgrading to a previous version that does not have this vulnerability. Use the command: 'npm install testpkgcwlib@5.0.1' to revert to the last known safe version.

Conclusion

The 'testpkgcwlib' package has a critical vulnerability that allows communication with a malicious domain, posing serious risks to applications. Users are urged to update to a patched version or implement workarounds to mitigate potential threats. Staying informed and proactive is essential for maintaining application security.

See every vulnerability recorded for testpkgcwlib →

Share this vulnerability

FAQ

The package communicates with a domain linked to malicious activities, which can compromise the security of applications using it.

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

If immediate updates are not possible, consider downgrading to a previous version of the package that does not have this vulnerability as a temporary workaround.

While specific exploits have not been publicly disclosed, the nature of the vulnerability suggests potential for data breaches and unauthorized access.

Regularly check the package repository for updates and consider using tools like Vulert to receive real-time alerts for vulnerabilities in your dependencies.

How To Fix

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

npm uninstall testpkgcwlib

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