Malicious Code Vulnerability in helpless_wren_z3n Package

helpless_wren_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94815: Malicious code in helpless_wren_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 helpless_wren_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 generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the helpless_wren_z3n package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting developers' ability to manage their packages and reputations effectively. The malicious payload can also introduce security risks by allowing unauthorized access to sensitive information.

How To Fix

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

npm uninstall helpless_wren_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 prevent the installation of this malicious package by using npm's package-lock.json file to lock your dependencies. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The helpless_wren_z3n package contains malicious code that poses significant risks to developers and their projects. By understanding the nature of this vulnerability and taking appropriate actions, such as uninstalling the package and using monitoring tools like Vulert, developers can safeguard their applications against potential threats.

See every vulnerability recorded for helpless_wren_z3n →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized modifications of your package metadata, potentially compromising your project's integrity and security.

You can check your package.json and package-lock.json files for the presence of helpless_wren_z3n. Additionally, using tools like Vulert can help identify vulnerabilities in your dependencies.

Immediately uninstall the package using 'npm uninstall helpless_wren_z3n' and monitor your project for any unusual behavior.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated with security advisories related to your packages.

While many packages are safe, it's essential to review package details, maintainers, and community feedback. Tools like Vulert can help you assess the security of packages.

How To Fix

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

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