Malicious Code Injection in secure_cicada_z3n Package

secure_cicada_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96487: Malicious code in secure_cicada_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 secure_cicada_z3n package is part of the npm ecosystem, primarily used for JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been linked to the proliferation of malicious packages on npm. This package is designed to inflate developer reputation scores through automated publishing of derivative packages, making it a target for vulnerabilities that can compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in the secure_cicada_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, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses significant risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall secure_cicada_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 measure, avoid using the secure_cicada_z3n package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The secure_cicada_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with compromised packages. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for secure_cicada_z3n →

Share this vulnerability

FAQ

The secure_cicada_z3n package is an npm package linked to a token reward campaign that has been found to contain malicious code.

The malicious code modifies your package.json, potentially leading to security vulnerabilities and the pollution of the npm registry.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If you have installed the secure_cicada_z3n package, you should uninstall it immediately and check your project for any dependencies that may have been affected.

Yes, tools like npm audit can help you identify vulnerabilities in your dependencies, and Vulert can provide real-time monitoring for open-source vulnerabilities.

How To Fix

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

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