Malicious Code Injection in ok_aphid_0xrequest Package - npm Vulnerability

ok_aphid_0xrequest Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106612: Malicious code in ok_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ok_aphid_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to users and the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the ok_aphid_0xrequest package arises from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which are then republished to the npm registry. The origin of this vulnerability is linked to a campaign aimed at exploiting the npm ecosystem for token rewards, leading to potential pollution of the registry and compromising the security of dependent projects.

How To Fix

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

npm uninstall ok_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 measure, you can prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies to known safe versions. You can also use the following command to audit your project for vulnerabilities: 'npm audit'.

Conclusion

The ok_aphid_0xrequest package poses a significant risk due to its malicious code that alters package metadata. It is crucial to remove this package from your project and monitor your dependencies regularly to maintain security. Utilizing tools like Vulert can aid in real-time monitoring for vulnerabilities.

See every vulnerability recorded for ok_aphid_0xrequest →

Share this vulnerability

FAQ

The ok_aphid_0xrequest package is a JavaScript package in the npm ecosystem that has been identified as malicious, associated with a token reward campaign.

This vulnerability can lead to unauthorized modifications of your project's package.json, potentially compromising its integrity and security.

You should uninstall the ok_aphid_0xrequest package immediately and audit your project for any other vulnerabilities.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your dependencies.

How To Fix

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

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