Malicious Code Injection in clear_stork_z3n Package - npm Vulnerability

clear_stork_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93579: Malicious code in clear_stork_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 clear_stork_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package, like many others in this campaign, is designed to automate the generation and publication of derivative packages. It aims to inflate developer reputation scores for token rewards, which can lead to the proliferation of malicious packages in the npm registry.

Vulnerability Detail

The vulnerability in the clear_stork_z3n package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. This behavior is part of a broader scheme to exploit the npm ecosystem, potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall clear_stork_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 workaround, you can avoid using the clear_stork_z3n package altogether. If it is already included in your project, you should remove it by running: npm uninstall clear_stork_z3n.

Conclusion

The clear_stork_z3n package poses a significant risk due to its malicious code that alters package.json files and contributes to npm registry pollution. It is essential to remove this package from your projects and monitor for any updates regarding a patched version.

See every vulnerability recorded for clear_stork_z3n →

Share this vulnerability

FAQ

The clear_stork_z3n package is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The package modifies package.json files to remove private flags, changes version numbers, and generates random package names, contributing to npm registry pollution.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

Currently, there is no patched version of the clear_stork_z3n package available. It is advisable to remove the package from your project.

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

How To Fix

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

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