Malicious Code Injection in thoughtful_ox_z3n: A Threat to npm Ecosystem

thoughtful_ox_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-97000: Malicious code in thoughtful_ox_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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

thoughtful_ox_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like others in the tea.xyz token reward scheme, is designed to manipulate the npm ecosystem by generating and publishing numerous derivative packages with the intent to inflate developer reputation scores. The package's functionality is compromised, making it a potential risk for developers who may unknowingly include it in their projects.

Vulnerability Detail

The vulnerability in thoughtful_ox_z3n stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to pollute the npm registry with derivative packages, which can lead to security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall thoughtful_ox_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 measure, you can avoid using the thoughtful_ox_z3n package and any other packages that are part of the tea.xyz token reward campaign. Monitor your project's dependencies closely and consider using tools like Vulert to identify vulnerabilities in your package-lock.json file.

Conclusion

The thoughtful_ox_z3n package poses a significant risk due to its malicious code designed to manipulate the npm ecosystem. It is crucial for developers to be vigilant about their dependencies, regularly check for vulnerabilities, and utilize tools like Vulert to maintain the security of their projects.

See every vulnerability recorded for thoughtful_ox_z3n →

Share this vulnerability

FAQ

thoughtful_ox_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm ecosystem.

The vulnerability can lead to unauthorized modifications in your package.json file, potentially compromising your project's security and integrity.

You should uninstall the thoughtful_ox_z3n package immediately using 'npm uninstall thoughtful_ox_z3n' and check your project for any other affected packages.

You can use Vulert, which monitors your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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