Malicious Code Injection in panicky_echidna_z3n: A Threat to npm Packages

panicky_echidna_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95829: Malicious code in panicky_echidna_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'panicky_echidna_z3n' is part of the npm ecosystem and has been identified as a malicious package associated with the tea.xyz token reward campaign. This package is designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. Its functionality is compromised, leading to potential security risks for users who integrate it into their projects.

Vulnerability Detail

The vulnerability in 'panicky_echidna_z3n' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior not only pollutes the npm registry but also poses a risk of unintentional exposure of sensitive information and undermines the integrity of the npm ecosystem. The package is part of a broader scheme to exploit the npm registry for token rewards, making it a significant threat.

How To Fix

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

npm uninstall panicky_echidna_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 installation of this malicious package by using the following command to uninstall it: npm uninstall panicky_echidna_z3n. Additionally, consider using a package-lock.json file to monitor dependencies and prevent the installation of known malicious packages.

Conclusion

The 'panicky_echidna_z3n' package poses a significant threat due to its malicious behavior aimed at manipulating the npm registry. It is essential for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities.

See every vulnerability recorded for panicky_echidna_z3n →

Share this vulnerability

FAQ

'panicky_echidna_z3n' is an npm package identified as malicious, part of a campaign to inflate developer reputation scores through automated package publishing.

The vulnerability can lead to the exposure of sensitive information and the pollution of the npm registry, compromising the integrity of your project.

You should uninstall 'panicky_echidna_z3n' immediately and check for any updates or patches that may address the vulnerability.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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