Critical Malicious Code Vulnerability in forkprove Package

forkprove Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20788: Malicious code in forkprove (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The forkprove package is an npm library designed to assist developers in managing and verifying code forks. It provides functionalities that enhance the development workflow by ensuring code integrity and facilitating version control. However, it has been identified to contain malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the forkprove package arises from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate further attacks on the system. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall forkprove

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, users can remove the forkprove package from their project until a secure version is released. This can be done using the command: 'npm uninstall forkprove'. Consider using alternative libraries that provide similar functionalities without the associated risks.

Conclusion

The forkprove package has been identified to contain malicious code, posing significant risks to users. Immediate action is required to update or remove the package to safeguard applications. Utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for forkprove →

Share this vulnerability

FAQ

Forkprove is an npm library that helps developers manage and verify code forks, enhancing their development workflow.

The malicious code in forkprove can lead to unauthorized access to sensitive data and may allow attackers to execute arbitrary commands.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If you cannot update the package right away, consider uninstalling it and using alternative libraries until a secure version is available.

Vulert monitors and alerts users in real-time for open-source vulnerabilities using just the package-lock.json file, providing a seamless way to stay informed.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall forkprove

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