Malicious Code Vulnerability in Forthcoming Pike Z3N Package

forthcoming_pike_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94581: Malicious code in forthcoming_pike_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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The forthcoming_pike_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 that aims to exploit npm's publishing system. It is designed to generate and publish derivative packages with random names, thereby inflating developer reputation scores for token rewards in the tea.xyz protocol. This behavior poses significant risks to developers and users relying on npm for secure package management.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the forthcoming_pike_z3n package, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to security risks and compromised package integrity. The malicious payload can affect any project that inadvertently includes this package, leading to reputational damage and security vulnerabilities.

How To Fix

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

npm uninstall forthcoming_pike_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 forthcoming_pike_z3n package and monitor your dependencies for any unauthorized changes. Regularly audit your npm packages using npm audit to identify and address vulnerabilities.

Conclusion

The forthcoming_pike_z3n package presents a significant security risk due to its malicious code designed to manipulate npm's publishing system. It is essential for developers to be vigilant and remove this package from their projects to maintain the integrity and security of their applications.

See every vulnerability recorded for forthcoming_pike_z3n →

Share this vulnerability

FAQ

It is an npm package identified as part of a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

Inclusion of this package can lead to security risks, including unauthorized modifications to your package.json file and potential exposure to malicious code.

You should uninstall the forthcoming_pike_z3n package immediately using the command npm uninstall forthcoming_pike_z3n.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected, without needing to sign up.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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