Malicious Code Injection in strict_bug_z3n Package

strict_bug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-90767: Malicious code in strict_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The strict_bug_z3n package is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The functionality of this package is compromised due to the presence of malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability in the strict_bug_z3n package originates from its association with malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly use this package, as it can lead to the installation of compromised dependencies.

How To Fix

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

npm uninstall strict_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, avoid using the strict_bug_z3n package and monitor your dependencies for any unauthorized changes. Regularly check your package-lock.json file for any unexpected modifications.

Conclusion

The strict_bug_z3n package is compromised by malicious code that alters its functionality and can lead to significant security risks. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for strict_bug_z3n →

Share this vulnerability

FAQ

The strict_bug_z3n package is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.

You can use Vulert to monitor your project for vulnerabilities. By analyzing your package-lock.json file, Vulert can alert you in real-time about any open-source vulnerabilities.

Using the strict_bug_z3n package poses risks such as the installation of compromised dependencies and potential exposure to malicious code that can affect your project's integrity.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using packages from untrusted sources.

If you have installed the strict_bug_z3n package, you should uninstall it immediately using the command: npm uninstall strict_bug_z3n.

How To Fix

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

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