Malicious Code Injection in convincing_loon_z3n Package

convincing_loon_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93802: Malicious code in convincing_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 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 convincing_loon_z3n package is part of the npm ecosystem, often associated with the tea.xyz token reward campaign. It is designed to facilitate the automatic generation and publication of derivative packages. This package, like others in its category, aims to inflate developer reputation scores for token rewards, but it has been compromised to include malicious functionalities.

Vulnerability Detail

The vulnerability in the convincing_loon_z3n package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of projects that depend on this package. The origin of this issue is linked to the broader trend of malicious packages flooding the npm ecosystem, specifically targeting developers involved in token reward campaigns.

How To Fix

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

npm uninstall convincing_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 remove the convincing_loon_z3n package from your project by executing: npm uninstall convincing_loon_z3n. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The convincing_loon_z3n package has been identified as containing malicious code that compromises the integrity of projects using it. It is essential to update or remove this package to safeguard your applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for convincing_loon_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to automate the generation of derivative packages.

The vulnerability allows the package to modify project files and continuously publish variants, which can lead to reputation inflation and registry pollution.

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 can temporarily uninstall the package to mitigate the risk until a secure version is released.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay informed about vulnerabilities in the packages you use.

How To Fix

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

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