Malicious Code Vulnerability in testy-tan-donkey Package

testy-tan-donkey Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96970: Malicious code in testy-tan-donkey (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The testy-tan-donkey package is part of the npm ecosystem, often used for various JavaScript applications. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This package, like others in the campaign, contains scripts designed to manipulate package metadata and publish numerous variants to the npm registry, leading to potential security risks.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the testy-tan-donkey package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants can lead to pollution of the npm registry, making it difficult for developers to identify legitimate packages. The ramifications include compromised package integrity and potential exploitation by malicious actors.

How To Fix

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

npm uninstall testy-tan-donkey

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, avoid using the testy-tan-donkey package and any other packages associated with the tea.xyz token reward campaign. Regularly monitor your package dependencies and remove any suspicious packages.

Conclusion

The testy-tan-donkey package contains malicious code that poses significant risks to developers and their applications. It is crucial to remove this package and any related packages from your project. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in your dependencies.

See every vulnerability recorded for testy-tan-donkey →

Share this vulnerability

FAQ

The testy-tan-donkey package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The malicious code modifies package metadata, leading to potential security risks and the pollution of the npm registry.

You should uninstall the testy-tan-donkey package immediately and monitor your project for any other suspicious packages.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid installing packages from untrusted sources.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall testy-tan-donkey

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