Malicious Code Injection in electrical_cicada_z3n Package

electrical_cicada_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102024: Malicious code in electrical_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 electrical_cicada_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the tea.xyz token reward system. It is designed to automatically generate and publish derivative packages, which can lead to a polluted npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability in the electrical_cicada_z3n package originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the proliferation of untrustworthy packages in the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses 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 electrical_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 workaround, you can avoid using the electrical_cicada_z3n package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The electrical_cicada_z3n package poses a significant security risk due to its malicious code that alters package metadata and proliferates untrustworthy packages. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for electrical_cicada_z3n →

Share this vulnerability

FAQ

The electrical_cicada_z3n package is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing of derivative packages.

This vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.

If you have installed the electrical_cicada_z3n package, it is recommended to remove it and update to a patched version or use an alternative package.

You can use Vulert to monitor your application for open-source vulnerabilities in real-time. By simply analyzing your package-lock.json file, Vulert alerts you to any potential issues.

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 electrical_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