Malicious Code Injection in mass_asp_0xrequest Package

mass_asp_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105648: Malicious code in mass_asp_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 mass_asp_0xrequest package is part of the npm ecosystem, typically used for various web development tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to manipulate its own metadata and publish variants that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the mass_asp_0xrequest package originates from its involvement in a token reward campaign that uses autopublish scripts to generate and publish numerous derivative packages. These scripts modify the package.json file to remove private flags, alter version numbers, and create random package names. This behavior can lead to pollution of the npm registry, making it difficult for developers to trust the packages they use. The malicious payload can also inflate developer reputation scores fraudulently, posing a risk to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall mass_asp_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 remove the mass_asp_0xrequest package from your project until a secure version is available. You can do this by executing the command: 'npm uninstall mass_asp_0xrequest'. Additionally, consider using Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The mass_asp_0xrequest package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential risks.

See every vulnerability recorded for mass_asp_0xrequest →

Share this vulnerability

FAQ

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

This vulnerability can lead to the pollution of the npm registry, making it difficult to trust the integrity of packages, and can also inflate developer reputation scores fraudulently.

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 cannot update the package, consider removing it from your project as a temporary measure until a secure version is released.

More information can be found in the vulnerability details provided by sources like Amazon Inspector and the package's repository.

How To Fix

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

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