Malicious Code Injection in initial_worm_z3n Package - npm Vulnerability

initial_worm_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104203: Malicious code in initial_worm_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 initial_worm_z3n package is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm ecosystem by automatically generating and publishing derivative packages. They aim to inflate developer reputation scores for token rewards, which can lead to a polluted npm registry and potential security risks for users relying on these packages.

Vulnerability Detail

The vulnerability in the initial_worm_z3n package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use 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 initial_worm_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 manually remove the initial_worm_z3n package from your project by running the command: npm uninstall initial_worm_z3n. Additionally, consider using a package manager that allows you to lock dependencies and monitor for vulnerabilities.

Conclusion

The initial_worm_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant about the packages they use and to regularly check for vulnerabilities. By following the recommended steps to remove the package and utilizing tools like Vulert, developers can protect their applications from potential threats.

See every vulnerability recorded for initial_worm_z3n →

Share this vulnerability

FAQ

The initial_worm_z3n package is part of a malicious campaign that floods the npm registry with derivative packages aimed at inflating developer reputation scores.

This vulnerability can lead to the introduction of malicious code in your application, potentially compromising its security and functionality.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If you have installed the initial_worm_z3n package, it is crucial to uninstall it immediately and monitor your application for any unusual behavior.

Yes, tools like Vulert can help you monitor your dependencies for vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

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