Malicious Code Injection in Nutritional Weasel Z3N Package

nutritious_weasel_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98840: Malicious code in nutritious_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 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 'nutritious_weasel_z3n' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been compromised to include malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the 'nutritious_weasel_z3n' package stems from its inclusion in a campaign that floods the npm registry with malicious packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate 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 nutritious_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 'nutritious_weasel_z3n' package altogether. If it is already installed, you can remove it by executing the following command in your terminal: npm uninstall nutritious_weasel_z3n.

Conclusion

The 'nutritious_weasel_z3n' package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to remove this package and monitor your dependencies for vulnerabilities to ensure the security of your projects.

See every vulnerability recorded for nutritious_weasel_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a token reward campaign but has been compromised to include malicious code.

The malicious code can alter your package metadata and potentially lead to security risks if the compromised package is used in your application.

You should uninstall the 'nutritious_weasel_z3n' package immediately to mitigate any risks.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

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