Malicious Code Injection in mild_spider_requirement Package

mild_spider_requirement Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95475: Malicious code in mild_spider_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 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 mild_spider_requirement package is part of the npm ecosystem, often utilized in various JavaScript projects. It is designed to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of derivative packages with harmful scripts.

Vulnerability Detail

The vulnerability in the mild_spider_requirement package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to significant security risks, including unauthorized access to sensitive data and the potential for further exploitation within the software supply chain.

How To Fix

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

npm uninstall mild_spider_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 mild_spider_requirement package from your project by executing the following command: npm uninstall mild_spider_requirement. This will prevent any malicious code from executing while you assess your project's dependencies.

Conclusion

The mild_spider_requirement package has been identified as containing malicious code that poses significant security risks. It is essential to take immediate action by updating or removing the package to protect your project from potential exploitation. Regular monitoring of your dependencies using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for mild_spider_requirement →

Share this vulnerability

FAQ

The mild_spider_requirement package is an npm package used in JavaScript projects for managing dependencies.

The vulnerability can lead to unauthorized modifications of your package.json file and the potential introduction of malicious code into your project.

You should immediately update the package to the latest version or remove it from your project to mitigate the risk.

You can use tools like Vulert, which monitors your package-lock.json file for 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.

How To Fix

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

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