Malicious Code Injection in intermediate_urial_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95102: Malicious code in intermediate_urial_requirement (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The intermediate_urial_requirement package is part of the npm ecosystem, which is widely used for JavaScript development. This package is suspected to be involved in a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to facilitate certain operations within JavaScript applications, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the intermediate_urial_requirement package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to inflate developer reputation scores through the automatic generation and publication of derivative packages, which can lead to pollution of the npm registry and potential security risks for developers using these packages.

How To Fix

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

npm uninstall intermediate_urial_requirement

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 intermediate_urial_requirement package from your project by executing the following command: npm uninstall intermediate_urial_requirement. This will prevent any malicious code from executing while you seek a secure alternative.

Conclusion

The intermediate_urial_requirement package has been identified as containing malicious code that poses a significant risk to developers and their applications. It is crucial to take immediate action to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for intermediate_urial_requirement →

Share this vulnerability

FAQ

It is a package in the npm ecosystem used in JavaScript development, but it has been compromised to include malicious code.

The malicious code modifies your package.json file and can lead to the publication of unauthorized packages, potentially compromising your application's security.

You should uninstall the package immediately and check for any updates or patches that may be available.

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

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

How To Fix

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

npm uninstall intermediate_urial_requirement

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