Malicious Code Vulnerability in essential_loon_0xrequest Package

essential_loon_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102239: Malicious code in essential_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 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 essential_loon_0xrequest package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to automate the generation and publishing of derivative packages, which can inflate developer reputation scores. However, this functionality has been exploited, leading to significant security concerns.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. It contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names, thereby polluting the npm registry. This can lead to unintended consequences for developers who may unknowingly use these compromised packages, potentially exposing their applications to further risks.

How To Fix

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

npm uninstall essential_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 essential_loon_0xrequest package and replace it with a trusted alternative that provides similar functionality. Additionally, regularly audit your package dependencies to identify and remove any malicious packages.

Conclusion

The essential_loon_0xrequest package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. Developers are advised to remove this package and monitor their dependencies closely to maintain application security.

See every vulnerability recorded for essential_loon_0xrequest →

Share this vulnerability

FAQ

It is an npm package associated with token reward campaigns that has been found to contain malicious code.

Using this package can lead to the modification of your package.json file and potentially expose your application to further vulnerabilities.

You should remove the essential_loon_0xrequest package from your project and monitor for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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