Malicious Code Injection in strategic_eagle_z3n: A Threat to npm Users

strategic_eagle_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-96802: Malicious code in strategic_eagle_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'strategic_eagle_z3n' 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 automatically generate and publish derivative packages with randomized names, which can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the 'strategic_eagle_z3n' package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to security risks, including the potential for developers to unknowingly use compromised packages, thereby exposing their applications to further vulnerabilities.

How To Fix

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

npm uninstall strategic_eagle_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 prevent the installation of this malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that your project does not include 'strategic_eagle_z3n' and regularly audit your dependencies using 'npm audit'.

Conclusion

The 'strategic_eagle_z3n' package poses a significant threat to npm users due to its malicious behavior of modifying package files and republishing variants. It is crucial to remove this package and monitor your dependencies to safeguard your applications from potential vulnerabilities.

See every vulnerability recorded for strategic_eagle_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.

You can use Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Using this package can expose your application to security vulnerabilities, as it modifies critical files and can lead to the installation of other malicious packages.

Regularly audit your dependencies using tools like npm audit, and consider using Vulert for real-time monitoring of open-source vulnerabilities.

While there is no direct automation for removal, using npm scripts to regularly audit and clean your dependencies can help maintain a secure environment.

How To Fix

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

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