Malicious Code Injection in parallel_ant_z3n: A Threat to npm Ecosystem

parallel_ant_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106899: Malicious code in parallel_ant_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 package 'parallel_ant_z3n' is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages, aimed at inflating developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in 'parallel_ant_z3n' stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, polluting the npm registry. This can lead to security risks, including the potential for executing malicious code in applications that depend on this package.

How To Fix

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

npm uninstall parallel_ant_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 workaround, you can avoid using the 'parallel_ant_z3n' package altogether. If it is a dependency of another package, consider looking for alternative packages that do not have known vulnerabilities.

Conclusion

The 'parallel_ant_z3n' package poses a significant risk due to its malicious code injection capabilities. It is essential to remove this package from your projects and monitor for any potential vulnerabilities using tools like Vulert. Staying vigilant and proactive can help safeguard your applications from such threats.

See every vulnerability recorded for parallel_ant_z3n →

Share this vulnerability

FAQ

The vulnerability can lead to the execution of malicious code and the pollution of the npm registry, affecting the integrity of applications that rely on this package.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should uninstall the package immediately using 'npm uninstall parallel_ant_z3n' and check for any other dependencies that may be affected.

Currently, there are no known patches for this specific package. It is recommended to remove it from your project.

Vulert monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software, ensuring you stay informed about potential threats.

How To Fix

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

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