Malicious Code Injection in sharp_flamingo_z3n: A Threat to npm Packages

sharp_flamingo_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108615: Malicious code in sharp_flamingo_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

sharp_flamingo_z3n is an npm package that has been identified as part of a broader malicious campaign targeting the npm ecosystem. This package, like others involved in the tea.xyz token reward scheme, is designed to manipulate the npm registry by creating and publishing numerous derivative packages with altered metadata. Its primary function is to inflate developer reputation scores for token rewards, which compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability in sharp_flamingo_z3n stems from its inclusion in a malicious campaign that utilizes scripts to automatically generate and publish derivative packages. These scripts modify the package.json file by removing private flags, changing version numbers, and creating random package names. This behavior not only pollutes the npm registry but can also lead to unintended consequences for developers who may unknowingly depend on these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has been flooding the npm ecosystem with such malicious packages.

How To Fix

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

npm uninstall sharp_flamingo_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 temporary workaround, you can avoid using sharp_flamingo_z3n and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies to ensure that no malicious packages are included in your project.

Conclusion

The sharp_flamingo_z3n package poses a significant threat due to its involvement in a malicious campaign that alters npm packages. It is crucial for developers to be vigilant, remove any affected packages, and utilize tools like Vulert to monitor their dependencies for vulnerabilities.

See every vulnerability recorded for sharp_flamingo_z3n →

Share this vulnerability

FAQ

sharp_flamingo_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

The vulnerability can lead to the inclusion of malicious code in your project, potentially compromising its security and integrity.

You should uninstall the package immediately using the command: npm uninstall sharp_flamingo_z3n.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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