Malicious Code Injection in Charming Harrier Z3N Package

charming_harrier_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93517: Malicious code in charming_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 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

Charming Harrier Z3N is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality is compromised by malicious scripts that alter its metadata and behavior.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the charming_harrier_z3n package. This code is designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. The malicious payload continuously republishes these altered packages to pollute the npm registry, posing a risk to developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm ecosystem, specifically targeting token reward systems.

How To Fix

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

npm uninstall charming_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, avoid using the charming_harrier_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your dependencies for vulnerabilities using tools like Vulert, which analyzes your package-lock.json for real-time alerts on open-source vulnerabilities.

Conclusion

The charming_harrier_z3n package has been compromised with malicious code that alters its metadata and behavior, posing significant risks to developers. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure your project remains secure.

See every vulnerability recorded for charming_harrier_z3n →

Share this vulnerability

FAQ

Charming_harrier_z3n is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

If your project uses the charming_harrier_z3n package, it may be at risk of having its metadata altered, leading to potential security issues and pollution of the npm registry.

You should uninstall the charming_harrier_z3n package immediately and check your package-lock.json for any remaining references to it.

You can use Vulert to monitor your project for open-source vulnerabilities by analyzing your package-lock.json file. Vulert provides real-time alerts 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 charming_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