Malicious Code Injection in front_stingray_z3n Package

front_stingray_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94625: Malicious code in front_stingray_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 front_stingray_z3n package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign that aims to exploit npm's package management system. This package, like others in its category, is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability stems from the package being associated with a malicious campaign that modifies the package.json file to remove private flags and change 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 dependency confusion and the introduction of harmful code into projects that rely on these packages.

How To Fix

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

npm uninstall front_stingray_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, you can avoid using the front_stingray_z3n package and replace it with a trusted alternative. Additionally, you can use npm audit to check for vulnerabilities in your project and take necessary actions.

Conclusion

The front_stingray_z3n package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert to ensure ongoing security.

See every vulnerability recorded for front_stingray_z3n →

Share this vulnerability

FAQ

front_stingray_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

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

You should remove the front_stingray_z3n package from your project immediately and check for any alternative packages that are safe to use.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

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