Malicious Code Injection in doubtful_tick_z3n Package

doubtful_tick_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101745: Malicious code in doubtful_tick_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

The doubtful_tick_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of such packages is to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the doubtful_tick_z3n package originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry, potential security risks for developers who unknowingly use these packages, and a compromised reputation system within the npm ecosystem.

How To Fix

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

npm uninstall doubtful_tick_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 doubtful_tick_z3n package and any packages that depend on it. Regularly audit your package dependencies using npm audit to identify and address vulnerabilities.

Conclusion

The doubtful_tick_z3n package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to be vigilant and remove any affected packages from their projects. Utilizing tools like Vulert can aid in maintaining a secure development environment.

See every vulnerability recorded for doubtful_tick_z3n →

Share this vulnerability

FAQ

The doubtful_tick_z3n package is an npm package that is part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the pollution of the npm registry and may introduce security risks if your project unknowingly depends on malicious packages.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

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

Yes, tools like Vulert can help monitor your package-lock.json for vulnerabilities in real-time, providing alerts for any issues found.

How To Fix

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

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