Malicious Code Injection in accepted_condor_z3n Package

accepted_condor_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-93094: Malicious code in accepted_condor_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 accepted_condor_z3n package is part of the npm ecosystem, often used in JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.

Vulnerability Detail

The vulnerability in the accepted_condor_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of applications that depend on this package. The malicious payload can also facilitate unauthorized access to sensitive information or resources, making it a significant security risk.

How To Fix

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

npm uninstall accepted_condor_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 accepted_condor_z3n package from your project by executing: npm uninstall accepted_condor_z3n. This will prevent the malicious code from executing until a secure version is available.

Conclusion

The accepted_condor_z3n package contains a serious vulnerability due to its involvement in a malicious campaign. It is crucial for developers to take immediate action to either remove or update the package to safeguard their applications from potential threats.

See every vulnerability recorded for accepted_condor_z3n →

Share this vulnerability

FAQ

The accepted_condor_z3n package is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores.

This vulnerability can lead to the pollution of the npm registry and may compromise the security of applications that rely on this package.

You should uninstall the package immediately or update it to a patched version if available.

Yes, you can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software without requiring access to the code or installation.

You can check if your application is affected by using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

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