Malicious Code Injection in worldwide_impala_z3n: npm Package Vulnerability

worldwide_impala_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111002: Malicious code in worldwide_impala_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 worldwide_impala_z3n package is part of a broader ecosystem within npm that has been exploited for malicious purposes. It is associated with the tea.xyz token reward campaign, which has led to the proliferation of numerous derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a target for malicious actors.

Vulnerability Detail

The vulnerability in the worldwide_impala_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 not only compromises 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 worldwide_impala_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 worldwide_impala_z3n package from your project by executing 'npm uninstall worldwide_impala_z3n'. This will prevent any potential exploitation until a secure version is released.

Conclusion

The worldwide_impala_z3n package has been identified as part of a malicious campaign that compromises the npm ecosystem. It is crucial for developers to be aware of this vulnerability, take necessary actions to update or remove the package, and utilize tools like Vulert for ongoing monitoring.

See every vulnerability recorded for worldwide_impala_z3n →

Share this vulnerability

FAQ

It is an npm package that has been linked to a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to the introduction of malicious code into your project, potentially compromising its security and integrity.

You should immediately uninstall the package and check for any updates or patches that may address the vulnerability.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time, alerting you to any issues without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

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