Malicious Code Injection in mobile_horse_z3n Package

mobile_horse_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105922: Malicious code in mobile_horse_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mobile_horse_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that floods the npm registry with harmful packages designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the mobile_horse_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores and pollute the npm registry with derivative packages. The malicious payload can lead to the unintentional installation of harmful code in applications that depend on this package, potentially compromising security and functionality.

How To Fix

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

npm uninstall mobile_horse_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 package by using npm's package-lock.json file to lock down dependencies. Ensure that your project does not include mobile_horse_z3n or any of its derivatives. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The mobile_horse_z3n package poses a significant risk due to its malicious code injection capabilities. It is crucial for developers to be vigilant about their dependencies and take immediate action to remove any affected packages. Utilizing tools like Vulert can help maintain the security of your applications by providing real-time vulnerability alerts.

See every vulnerability recorded for mobile_horse_z3n →

Share this vulnerability

FAQ

The mobile_horse_z3n package is an npm package that has been identified as part of a malicious campaign to manipulate developer reputation scores.

If your application depends on the mobile_horse_z3n package, it may inadvertently execute malicious code, compromising security and functionality.

You should uninstall the mobile_horse_z3n package immediately and check your package-lock.json file for any references to it.

You can use tools like Vulert, which monitors your package-lock.json file for open-source 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 signing up.

How To Fix

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

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