Malicious Code Injection in mobile_snipe_z3n Package

mobile_snipe_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105924: Malicious code in mobile_snipe_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 mobile_snipe_z3n package is part of the npm ecosystem, typically used for mobile application development. However, it has been identified as a malicious package involved in a token reward campaign that exploits npm's publishing system. This package is designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the mobile_snipe_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 significant security risks, including the potential for code injection and unauthorized access to systems using this package.

How To Fix

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

npm uninstall mobile_snipe_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 avoid using the mobile_snipe_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file using tools like Vulert to detect any vulnerabilities in real-time.

Conclusion

The mobile_snipe_z3n package poses a significant security risk due to its malicious behavior of modifying package files and republishing variants. It is essential to remove this package and monitor your project for vulnerabilities using tools like Vulert to ensure the security of your applications.

See every vulnerability recorded for mobile_snipe_z3n →

Share this vulnerability

FAQ

The mobile_snipe_z3n package is an npm package that has been identified as malicious, involved in a scheme to inflate developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially allowing malicious code to be executed within your application.

If you have installed the mobile_snipe_z3n package, it is crucial to remove it immediately and check for any other affected packages in your project.

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

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

How To Fix

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

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