Malicious Code Detected in testt-tester Package - Security Alert

testt-tester Updated 02 Oct 2025

Summary

06/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6858: Malicious code in testt-tester (npm). Affects testt-tester 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 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 testt-tester package is an npm library designed for testing purposes within JavaScript applications. It provides developers with tools to facilitate testing workflows and improve code quality. However, this package has been identified as having a serious security vulnerability that allows it to communicate with a domain associated with malicious activity, potentially compromising user data and application integrity.

Vulnerability Detail

The vulnerability in the testt-tester package originates from its ability to connect to a malicious domain. This connection can lead to unauthorized data access, data exfiltration, or even remote code execution, depending on the nature of the malicious activities associated with the domain. The issue was introduced in version 1.0.0 and poses significant risks to any application utilizing this package, as it can be exploited by attackers to gain control over the affected systems.

How To Fix

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

npm uninstall testt-tester

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, you can remove the testt-tester package from your project until a secure version is released. Use the following command to uninstall the package: 'npm uninstall testt-tester'. This will prevent any potential malicious activity while you await a fix.

Conclusion

The testt-tester package has been flagged for containing malicious code that can compromise application security. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Regular monitoring for vulnerabilities is essential to maintain software integrity.

See every vulnerability recorded for testt-tester →

Share this vulnerability

FAQ

The testt-tester package is an npm library used for testing JavaScript applications, providing tools to enhance testing workflows.

The vulnerability allows the package to communicate with a malicious domain, which can lead to data breaches or unauthorized access to your application.

Currently, there is no specific patch mentioned for the testt-tester package. It is advisable to monitor the package repository for updates.

If you are using the testt-tester package, you should consider uninstalling it until a secure version is released or monitor for updates regularly.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the 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 testt-tester

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