Malicious Code Exploit in proper_aphid_0xrequest Package

proper_aphid_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107352: Malicious code in proper_aphid_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 proper_aphid_0xrequest package is part of the npm ecosystem, typically used for various JavaScript 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 within the npm ecosystem.

Vulnerability Detail

The vulnerability in the proper_aphid_0xrequest package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall proper_aphid_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, avoid using the proper_aphid_0xrequest package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The proper_aphid_0xrequest package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the affected package, and utilize tools like Vulert to monitor their projects for potential threats.

See every vulnerability recorded for proper_aphid_0xrequest →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the installation of malicious code, which may compromise your project's security and integrity.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

You should uninstall the proper_aphid_0xrequest package immediately and review your project's dependencies for any other potential vulnerabilities.

Yes, tools like Vulert can help monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

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