Malicious Code Injection in universal_loon_0xrequest: A Threat to npm Packages

universal_loon_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110144: Malicious code in universal_loon_0xrequest (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 package 'universal_loon_0xrequest' is part of a broader ecosystem of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in 'universal_loon_0xrequest' stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants, leading to pollution of the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages. The ramifications include potential security risks for applications using these packages, as they may inadvertently incorporate malicious code.

How To Fix

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

npm uninstall universal_loon_0xrequest

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 'universal_loon_0xrequest' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like Vulert to monitor for vulnerabilities.

Conclusion

The 'universal_loon_0xrequest' package poses a significant risk due to its malicious behavior, which can compromise the integrity of your npm projects. It is crucial to remove this package and monitor your dependencies for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for universal_loon_0xrequest →

Share this vulnerability

FAQ

The main issue is that it contains malicious code that modifies package.json files and repackages itself, leading to pollution of the npm registry.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you have installed this package, you should uninstall it immediately using 'npm uninstall universal_loon_0xrequest' and check your package-lock.json for any references.

Yes, consider looking for other npm packages that provide similar functionality but do not have known vulnerabilities.

Regularly audit your npm packages using tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall universal_loon_0xrequest

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