Malicious Code Injection in electoral_cuckoo_z3n Package

electoral_cuckoo_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94204: Malicious code in electoral_cuckoo_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 electoral_cuckoo_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity.

Vulnerability Detail

The vulnerability in the electoral_cuckoo_z3n package stems from its inclusion in a malicious campaign that uses autopublish scripts to modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. The malicious payload can potentially affect developers by compromising their projects and reputations, as well as cluttering the npm ecosystem with unwanted packages.

How To Fix

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

npm uninstall electoral_cuckoo_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 remove the electoral_cuckoo_z3n package from your project by executing the following command: npm uninstall electoral_cuckoo_z3n. This will help mitigate the risk until a fixed version is available.

Conclusion

The electoral_cuckoo_z3n package contains malicious code that can compromise your project's integrity and pollute the npm registry. It is crucial to update or remove this package to mitigate risks. Utilizing tools like Vulert can help you monitor for such vulnerabilities in real-time.

See every vulnerability recorded for electoral_cuckoo_z3n →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code can modify your package.json file, remove private flags, and clutter the npm registry with unwanted packages, potentially harming your project's integrity.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner without any signup.

If you cannot update the package, consider removing it from your project as a temporary measure to mitigate risks.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

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