Malicious Code Injection in weekly_bug_z3n: A Threat to npm Packages

weekly_bug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-92185: Malicious code in weekly_bug_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 package 'weekly_bug_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized by developers to share and manage code libraries. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages. This vulnerability poses a significant risk to the integrity of the npm registry and the security of applications relying on this package.

Vulnerability Detail

The vulnerability in 'weekly_bug_z3n' originates from its association with the tea.xyz token reward campaign, which floods the npm registry with malicious packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also compromises the security of applications that depend on these packages, potentially allowing for further exploitation.

How To Fix

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

npm uninstall weekly_bug_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 'weekly_bug_z3n' package and replace it with a reputable alternative. Always verify the integrity of packages before including them in your project.

Conclusion

The 'weekly_bug_z3n' package presents a significant security threat due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove this package from their projects to maintain the integrity and security of their applications.

See every vulnerability recorded for weekly_bug_z3n →

Share this vulnerability

FAQ

The 'weekly_bug_z3n' package is an npm package that has been identified as malicious, designed to inflate developer reputation scores through the creation of numerous derivative packages.

This vulnerability can compromise the integrity of your application by introducing malicious code that may lead to further exploitation or data breaches.

If you have installed 'weekly_bug_z3n', you should uninstall it immediately using 'npm uninstall weekly_bug_z3n' and check for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can also check your application against known vulnerabilities using the Vulert playground.

There is no patch for 'weekly_bug_z3n' as it is a malicious package. The best course of action is to remove it from your project.

How To Fix

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

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