Malicious Code Injection in testy_lemur_z3n: A Threat to npm Packages

testy_lemur_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96977: Malicious code in testy_lemur_z3n (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 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

testy_lemur_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the campaign, is designed to manipulate the npm ecosystem by generating and publishing derivative packages with randomized names. The primary function of this package is to inflate developer reputation scores for token rewards associated with the tea.xyz protocol, making it a significant threat to the integrity of the npm registry.

Vulnerability Detail

The vulnerability in testy_lemur_z3n originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall testy_lemur_z3n

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 avoid using the testy_lemur_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the source and integrity of packages before installation.

Conclusion

The testy_lemur_z3n package poses a significant threat due to its malicious code that manipulates the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action if they have installed this package. Regular monitoring and using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for testy_lemur_z3n →

Share this vulnerability

FAQ

The main issue is that it contains malicious code designed to manipulate the npm registry and inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected.

You should uninstall the package immediately using the command 'npm uninstall testy_lemur_z3n' and look for alternative packages.

Yes, using this package can lead to security breaches, as it modifies your project's package.json and can introduce vulnerabilities.

Always verify the source of npm packages, keep your dependencies updated, and utilize tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall testy_lemur_z3n

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