Malicious Code Injection in universal_loon_z3n: A Threat to npm Packages

universal_loon_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110145: Malicious code in universal_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 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 package 'universal_loon_z3n' is part of a series of npm packages that have been identified as malicious. These packages are often linked to token reward campaigns, specifically the tea.xyz protocol, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of these packages lies in their ability to modify critical files and continuously republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability in 'universal_loon_z3n' originates from its association with a malicious campaign that employs scripts to alter the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The ramifications of this vulnerability are significant, as it can lead to the proliferation of unwanted packages in the npm registry, potentially compromising the integrity of applications that rely on npm for package management.

How To Fix

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

npm uninstall universal_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 measure, you can avoid using the 'universal_loon_z3n' package and check your project for any dependencies that may have been affected by this malicious package. You can use the following command to check for vulnerabilities in your project: 'npm audit'.

Conclusion

The 'universal_loon_z3n' package poses a significant threat due to its malicious code that modifies essential package files and repopulates the npm registry with unwanted variants. It is crucial for developers to remove this package and monitor their projects for similar vulnerabilities to maintain application integrity.

See every vulnerability recorded for universal_loon_z3n →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that modifies package files to inflate developer reputation scores.

The vulnerability can lead to the introduction of unwanted packages in your application, potentially compromising its security and integrity.

You should uninstall the 'universal_loon_z3n' package immediately and check your project for any other affected dependencies.

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

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

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 universal_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