Critical Malicious Code Vulnerability in gifhorse-cli Package

gifhorse-cli Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21410: Malicious code in gifhorse-cli (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The gifhorse-cli package is a command-line interface tool designed for generating GIFs from images. It is widely used in various projects for its simplicity and efficiency. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the gifhorse-cli package stems from the inclusion of malicious code that can compromise user systems. This code may allow unauthorized access, data exfiltration, or other harmful actions. The issue was introduced in version 0 and affects all subsequent versions. Users of this package are at risk of severe consequences, including data loss and system integrity breaches.

How To Fix

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

npm uninstall gifhorse-cli

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, consider removing the gifhorse-cli package from your project until a secure version is released. You can do this by running: npm uninstall gifhorse-cli.

Conclusion

The discovery of malicious code in the gifhorse-cli package highlights the importance of maintaining secure dependencies in software projects. Users are urged to update or remove the package to protect their systems from potential threats. Regular monitoring for vulnerabilities is essential for maintaining application security.

See every vulnerability recorded for gifhorse-cli →

Share this vulnerability

FAQ

gifhorse-cli is a command-line tool used for generating GIFs from images, popular for its ease of use.

The malicious code can potentially allow unauthorized access to user systems, leading to data breaches and other security issues.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

If an immediate update is not possible, consider uninstalling the package as a temporary workaround to mitigate risks.

Utilize tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities.

How To Fix

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

npm uninstall gifhorse-cli

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