Malicious Code Injection in prepared_harrier_z3n Package

prepared_harrier_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89503: Malicious code in prepared_harrier_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The prepared_harrier_z3n package is part of the npm ecosystem, primarily used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with derivative packages. These packages often contain scripts that manipulate package metadata and publish new variants to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in the prepared_harrier_z3n package stems from 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 these variants. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aims to exploit npm's publishing mechanisms, potentially polluting the npm registry and compromising the integrity of the ecosystem.

How To Fix

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

npm uninstall prepared_harrier_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 prevent the malicious behavior by removing the prepared_harrier_z3n package from your project. Use the following command:

npm uninstall prepared_harrier_z3n

Additionally, monitor your package-lock.json file for any unauthorized changes.

Conclusion

The prepared_harrier_z3n package contains a serious vulnerability due to malicious code that alters package metadata. It is crucial to update or remove this package to maintain the integrity of your project. Utilizing tools like Vulert can help you stay informed about vulnerabilities in your dependencies.

See every vulnerability recorded for prepared_harrier_z3n →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized changes in your project's package.json, potentially compromising your project's integrity and security.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

If no patched version is available, consider removing the package from your project and looking for alternative solutions.

The campaign floods the npm registry with malicious packages designed to inflate developer reputation scores, leading to vulnerabilities like the one found in prepared_harrier_z3n.

How To Fix

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

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