Malicious Code Injection in fascinating_kingfisher_0xrequest Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102572: Malicious code in fascinating_kingfisher_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The fascinating_kingfisher_0xrequest package is part of the npm ecosystem, which is widely used for JavaScript development. This package was identified as part of a token reward campaign that aimed to manipulate npm's package registry. It is designed to facilitate the automatic generation and publication of derivative packages, which can lead to reputation inflation for developers involved in the tea protocol token rewards.

Vulnerability Detail

The vulnerability in the fascinating_kingfisher_0xrequest package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can clutter the npm registry. This behavior is part of a broader scheme to inflate developer reputation scores, potentially leading to security risks and the proliferation of untrustworthy packages in the ecosystem.

How To Fix

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

npm uninstall fascinating_kingfisher_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 fascinating_kingfisher_0xrequest package and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The fascinating_kingfisher_0xrequest package poses a significant risk due to its malicious code that manipulates the npm registry. It is crucial for developers to remove this package from their projects and stay vigilant about potential vulnerabilities in their dependencies.

See every vulnerability recorded for fascinating_kingfisher_0xrequest →

Share this vulnerability

FAQ

It is an npm package that was part of a token reward campaign, designed to manipulate the npm registry.

The vulnerability can lead to the proliferation of untrustworthy packages and may compromise the integrity of your project's dependencies.

You should uninstall the package immediately and monitor your project for any related issues.

Currently, there is no patched version available. The best course of action is to remove the package.

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

How To Fix

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

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