Critical Malicious Code Vulnerability in super-commit Package

super-commit Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191015: Malicious code in super-commit (npm). Affects super-commit versions 1.0.1. 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 super-commit package is an npm library designed for automating commit messages in version control systems. It aims to simplify the process of creating meaningful commit messages based on the changes made in the codebase. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the super-commit package. This code can potentially allow unauthorized access to the system, leading to the compromise of sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by security sources, indicating that any system running this package should be considered fully compromised. Users are advised to take immediate action to mitigate the risks associated with this vulnerability.

How To Fix

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

npm uninstall super-commit

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 workaround, you can temporarily disable the functionalities that rely on the super-commit package until it is removed or patched. However, this does not mitigate the risk of having the malicious code present on your system.

Conclusion

The discovery of malicious code within the super-commit package poses a significant security threat to any system that has it installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their software.

See every vulnerability recorded for super-commit →

Share this vulnerability

FAQ

You should immediately remove the super-commit package and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to remove the package could lead to unauthorized access to your system, potentially compromising sensitive data.

Yes, but you may need to find alternative solutions for the functionalities that relied on the super-commit package.

How To Fix

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

npm uninstall super-commit

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