Malicious Code Vulnerability in shaky_kingfisher_z3n Package

shaky_kingfisher_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96543: Malicious code in shaky_kingfisher_z3n (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 shaky_kingfisher_z3n package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods npm with derivative packages, impacting developers' reputations and the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package being associated with the tea.xyz token reward campaign, which employs autopublish scripts to create and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential security risks for developers using these packages.

How To Fix

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

npm uninstall shaky_kingfisher_z3n

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 workaround, you can temporarily avoid using the shaky_kingfisher_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall shaky_kingfisher_z3n.

Conclusion

The shaky_kingfisher_z3n package poses a significant risk due to its association with malicious activities aimed at inflating developer reputation scores. It is essential to remove this package from your project and monitor for any updates or patches. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for shaky_kingfisher_z3n →

Share this vulnerability

FAQ

shaky_kingfisher_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the creation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project and affecting its security.

You should uninstall the shaky_kingfisher_z3n package immediately and look for alternative packages to avoid security risks.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

Regularly update your dependencies, review changelogs for security fixes, and utilize tools like Vulert to monitor for vulnerabilities in your project.

How To Fix

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

npm uninstall shaky_kingfisher_z3n

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