Malicious Code Injection in tender_loon_z3n: npm Package Vulnerability

tender_loon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96953: Malicious code in tender_loon_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The 'tender_loon_z3n' package is part of the tea.xyz token reward campaign that has recently infiltrated the npm ecosystem. This package is designed to automate the generation and publication of derivative packages, which are often used to inflate developer reputation scores for token rewards. The malicious nature of this package lies in its ability to modify critical files and republish variants that can clutter the npm registry.

Vulnerability Detail

The vulnerability in 'tender_loon_z3n' originates from its inclusion in a malicious campaign that employs scripts to automatically publish derivative packages with randomized names. This behavior not only modifies the package.json file by removing private flags and changing version numbers but also generates random package names, leading to potential pollution of the npm registry. The ramifications include compromised developer reputations and the risk of inadvertently using malicious packages in projects.

How To Fix

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

npm uninstall tender_loon_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 'tender_loon_z3n' package and replace it with a trusted alternative. Additionally, you can monitor your project for any unauthorized changes to the package.json file.

Conclusion

The 'tender_loon_z3n' package poses a significant risk due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to be vigilant about the packages they use and to take immediate action if they find this package in their projects.

See every vulnerability recorded for tender_loon_z3n →

Share this vulnerability

FAQ

The 'tender_loon_z3n' package is part of a malicious campaign that automates the creation and publication of npm packages to inflate developer reputation scores.

This vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing malicious code.

You should uninstall the package immediately using the command: npm uninstall tender_loon_z3n.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall tender_loon_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