Malicious Code Vulnerability in appalling_reindeer_z3n Package

appalling_reindeer_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99507: Malicious code in appalling_reindeer_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The appalling_reindeer_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate npm's publishing system by creating and publishing numerous derivative packages with randomized names. This behavior aims to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised due to its malicious intent, making it a significant risk for developers using it.

Vulnerability Detail

The vulnerability originates from the appalling_reindeer_z3n package, which contains scripts that automatically modify the package.json file. These modifications include removing private flags, altering version numbers, and generating random package names, which leads to the continuous republishing of variants. This behavior pollutes the npm registry and can potentially harm developers' reputations and the integrity of their projects. The malicious payload is designed to exploit the npm ecosystem, making it a serious concern for users.

How To Fix

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

npm uninstall appalling_reindeer_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 appalling_reindeer_z3n package from being used in your project by adding it to your .npmrc file with the following line: package-lock=false. This will stop npm from installing this package until you can remove it completely.

Conclusion

The appalling_reindeer_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package from their projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for appalling_reindeer_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, potentially harming your project's integrity and reputation by introducing unwanted packages.

You should uninstall the appalling_reindeer_z3n package immediately using the command npm uninstall appalling_reindeer_z3n.

Yes, you can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time 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 appalling_reindeer_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