Malicious Code Injection in efficient_asp_0xrequest Package

efficient_asp_0xrequest Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101893: Malicious code in efficient_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 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 efficient_asp_0xrequest package is part of the npm ecosystem, typically used for handling HTTP requests in JavaScript applications. It is often utilized in web development to streamline communication between clients and servers. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to significant security risks.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the efficient_asp_0xrequest package. This payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which are then continuously republished to the npm registry. This behavior not only pollutes the npm ecosystem but also compromises the integrity of applications relying on this package, potentially leading to unauthorized access or data breaches.

How To Fix

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

npm uninstall efficient_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 avoid using the efficient_asp_0xrequest package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider locking your dependencies to known safe versions in your package-lock.json file.

Conclusion

The efficient_asp_0xrequest package poses a significant security risk due to its malicious code that alters package configurations and republishing behavior. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain application security.

See every vulnerability recorded for efficient_asp_0xrequest →

Share this vulnerability

FAQ

It is an npm package used for handling HTTP requests in JavaScript applications.

The malicious code can modify your package.json, remove private flags, and republish variants, leading to potential security breaches.

You should uninstall the package immediately and check for alternative solutions or patches.

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

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

How To Fix

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

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