Malicious Code Injection in obvious_guan_z3n Package - npm Vulnerability

obvious_guan_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95722: Malicious code in obvious_guan_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 obvious_guan_z3n package is part of a series of npm packages that emerged during 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 malicious nature of this package lies in its ability to modify critical files and republish variants, leading to potential abuse within the npm ecosystem.

Vulnerability Detail

This vulnerability originates from the package's design, which includes autopublish scripts that manipulate the package.json file. It removes private flags, alters version numbers, and generates random package names, effectively polluting the npm registry. The ramifications include the potential for developers to unknowingly install malicious packages, compromising their applications and systems.

How To Fix

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

npm uninstall obvious_guan_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 obvious_guan_z3n package and monitor your project for any dependencies that may have inadvertently included it. Regularly audit your npm packages using tools like npm audit to identify and address vulnerabilities.

Conclusion

The obvious_guan_z3n package poses a significant risk due to its malicious code designed to manipulate npm packages. It is essential to remove this package from your projects and monitor for any related vulnerabilities to ensure the security of your applications.

See every vulnerability recorded for obvious_guan_z3n →

Share this vulnerability

FAQ

obvious_guan_z3n is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated package publishing.

The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Immediately uninstall the package using npm uninstall obvious_guan_z3n and check your package-lock.json for any references.

Yes, tools like npm audit and Vulert can help you identify and manage vulnerabilities in your npm packages.

How To Fix

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

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