Malicious Code Injection in flaky_weasel_z3n Package

flaky_weasel_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94536: Malicious code in flaky_weasel_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

The flaky_weasel_z3n package is part of the npm ecosystem and has been identified as part of a malicious campaign targeting developers through the tea.xyz token reward system. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names, ultimately aiming to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata.

Vulnerability Detail

The vulnerability originates from the package's association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall flaky_weasel_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 measure, you can avoid using flaky_weasel_z3n and any packages that may have been derived from it. Regularly audit your package-lock.json file to identify and remove any suspicious packages.

Conclusion

The flaky_weasel_z3n package poses a significant security risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their dependencies for any potential vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for flaky_weasel_z3n →

Share this vulnerability

FAQ

Flaky_weasel_z3n is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and instability in your application.

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

If you have installed flaky_weasel_z3n, you should uninstall it immediately using 'npm uninstall flaky_weasel_z3n' and audit your dependencies for any other malicious packages.

Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and stay informed about security advisories related to the packages you use.

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 flaky_weasel_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