Malicious Code Injection in inquisitive_mole_0xrequest Package

inquisitive_mole_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104244: Malicious code in inquisitive_mole_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The inquisitive_mole_0xrequest package is part of the npm ecosystem, often used in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant issues in the integrity and security of applications that rely on them.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the inquisitive_mole_0xrequest package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The primary risk is that it allows unauthorized access and manipulation of the npm registry, potentially leading to the distribution of compromised packages. This can severely impact applications that depend on this package, exposing them to security threats and instability.

How To Fix

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

npm uninstall inquisitive_mole_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 prevent the installation of this malicious package by using npm's package-lock.json file to lock down your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The inquisitive_mole_0xrequest package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to take immediate action by removing this package and monitoring their projects for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for inquisitive_mole_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

It can lead to unauthorized modifications of your package dependencies, potentially introducing security risks and instability.

You should uninstall the inquisitive_mole_0xrequest package immediately and check for any other affected packages.

Yes, you can use Vulert to monitor your project in real-time for open-source vulnerabilities without needing to access the code.

Regularly update your packages, use tools like Vulert for monitoring, and review your package-lock.json file for any unauthorized changes.

How To Fix

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

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