Malicious Code Injection in live_weasel_z3n Package - npm Vulnerability

live_weasel_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95286: Malicious code in live_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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The live_weasel_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the live_weasel_z3n package originates from its involvement in the tea.xyz token reward campaign. It contains malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the affected package but also contributes to the degradation of the npm ecosystem by continuously republishing variants, making it difficult for developers to trust the packages they use.

How To Fix

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

npm uninstall live_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 workaround, you can avoid using the live_weasel_z3n package altogether. If it is already in your project, consider removing it and replacing it with a trusted alternative. You can also use the following command to uninstall the package: npm uninstall live_weasel_z3n.

Conclusion

The live_weasel_z3n package poses a significant risk due to its malicious code that alters package configurations and floods the npm registry. It is essential to remove this package from your project and monitor for any vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your software.

See every vulnerability recorded for live_weasel_z3n →

Share this vulnerability

FAQ

The live_weasel_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can compromise your project's integrity by introducing malicious code that modifies package configurations and floods the npm registry.

You should uninstall the live_weasel_z3n package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities in real-time. It utilizes package-lock.json to alert you of any issues.

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

How To Fix

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

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