Malicious Code Injection in pale_horse-gooddev Package

pale_horse-gooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106885: Malicious code in pale_horse-gooddev (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 pale_horse-gooddev package is part of the npm ecosystem, which is widely used for JavaScript development. This package is associated with a token reward campaign that has led to the proliferation of malicious packages on npm. Its primary function is to facilitate the development and distribution of JavaScript applications, but it has been compromised to serve malicious purposes.

Vulnerability Detail

The vulnerability in the pale_horse-gooddev package stems from its involvement in the tea.xyz token reward campaign. This package contains malicious scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. These actions are intended to inflate developer reputation scores and pollute the npm registry with derivative packages. The malicious payload can lead to security risks, including unauthorized access to sensitive information and the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall pale_horse-gooddev

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, consider removing the pale_horse-gooddev package from your project until a secure version is released. You can do this by executing the following command: npm uninstall pale_horse-gooddev.

Conclusion

The pale_horse-gooddev package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial to take immediate action by updating or removing the package to mitigate potential risks. Regular monitoring of dependencies is recommended to ensure the security of your applications.

See every vulnerability recorded for pale_horse-gooddev →

Share this vulnerability

FAQ

The pale_horse-gooddev package is an npm package used in JavaScript development, but it has been compromised to include malicious code.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially exposing your application to further security risks.

If you have installed the pale_horse-gooddev package, it is recommended to uninstall it immediately and monitor your application for any unusual behavior.

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

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 pale_horse-gooddev

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