Malicious Code Detected in cool-testing-7-9-2016 Package

cool-testing-7-9-2016 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17536: Malicious code in cool-testing-7-9-2016 (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 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 package 'cool-testing-7-9-2016' is an npm module designed for testing purposes. It was intended to facilitate various testing scenarios in JavaScript applications. However, it has been identified to contain malicious code, which poses significant risks to users who integrate it into their projects. This vulnerability can lead to unauthorized access, data breaches, or other harmful actions within the application.

Vulnerability Detail

The vulnerability in the 'cool-testing-7-9-2016' package stems from the inclusion of malicious code that can execute harmful operations when the package is used. This code may compromise the security of applications that rely on this package, potentially leading to data loss or unauthorized access to sensitive information. The malicious code was introduced in all versions starting from 0, making it imperative for users to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall cool-testing-7-9-2016

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, you can temporarily disable any functionality that relies on the 'cool-testing-7-9-2016' package until it is removed or replaced. Additionally, you can monitor your application for any unusual behavior that may arise from the use of this package.

Conclusion

The 'cool-testing-7-9-2016' package has been identified as containing malicious code, posing significant risks to users. It is crucial to remove this package from your projects and replace it with secure alternatives. Regular monitoring of your dependencies using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for cool-testing-7-9-2016 →

Share this vulnerability

FAQ

It is an npm module designed for testing purposes in JavaScript applications.

The package contains code that can execute harmful operations, potentially compromising application security.

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.

You should uninstall the package immediately and replace it with a secure alternative.

Yes, there are several reputable testing packages available on npm that do not have known vulnerabilities. Always check the package's security status before use.

How To Fix

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

npm uninstall cool-testing-7-9-2016

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