Malicious Code Injection in integral_pike_z3n Package

integral_pike_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95060: Malicious code in integral_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 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 integral_pike_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. It is designed to facilitate the distribution of token rewards but has been compromised to include malicious scripts. These scripts are intended to manipulate package metadata and inflate developer reputation scores by generating numerous derivative packages with random names.

Vulnerability Detail

The vulnerability in the integral_pike_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to clutter the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall integral_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 workaround, you can remove the integral_pike_z3n package from your project by executing 'npm uninstall integral_pike_z3n'. This will prevent any malicious scripts from executing until a secure version is available.

Conclusion

The integral_pike_z3n package has been identified as containing malicious code that can compromise the integrity of projects using it. It is essential to take immediate action to remove or update the package to safeguard your development environment.

See every vulnerability recorded for integral_pike_z3n →

Share this vulnerability

FAQ

The integral_pike_z3n package is part of the npm ecosystem and is linked to the tea.xyz token reward campaign, which has been compromised to include malicious code.

The vulnerability can lead to the modification of your project's package.json file, potentially exposing it to further attacks and cluttering the npm registry with malicious packages.

If you have installed the integral_pike_z3n package, it is crucial to uninstall it immediately and check for any updates or patches.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

More information can be found in the vulnerability report on the GitHub repository for malicious packages or by consulting the npm registry.

How To Fix

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

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