Malicious Code Vulnerability in apparent_kingfisher_0xrequest Package
Summary
MAL-2025-99517: Malicious code in apparent_kingfisher_0xrequest (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The apparent_kingfisher_0xrequest package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. However, this functionality has been exploited to introduce malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability originates from the apparent_kingfisher_0xrequest package, which is linked to a campaign that floods the npm registry with malicious packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the pollution of the npm registry and can potentially harm developers by misrepresenting their contributions and reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall apparent_kingfisher_0xrequestIf 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 apparent_kingfisher_0xrequest package and any other packages associated with the tea.xyz token reward campaign. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The apparent_kingfisher_0xrequest package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to remove this package and monitor their dependencies to maintain the integrity of their projects.
See every vulnerability recorded for apparent_kingfisher_0xrequest →
FAQ
It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and misrepresenting your contributions.
You should uninstall the apparent_kingfisher_0xrequest package immediately and check your project for any other compromised dependencies.
Yes, you can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
