Malicious Code Detected in apex-promise-transport-commitizen: A Critical Security Alert

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14634: Malicious code in apex-promise-transport-commitizen (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 package apex-promise-transport-commitizen is an npm module designed to facilitate the transport of promises in a commitizen environment. It is utilized by developers to streamline the process of creating standardized commit messages. However, this package has been found to contain malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in apex-promise-transport-commitizen arises from the inclusion of malicious code within the package. This code can potentially compromise the security of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security threats.

How To Fix

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

npm uninstall apex-promise-transport-commitizen

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, you can avoid using apex-promise-transport-commitizen until a secure version is released. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the apex-promise-transport-commitizen package underscores the importance of vigilance when using third-party libraries. Developers are advised to remove the package and monitor for updates or alternatives to ensure the security of their applications.

See every vulnerability recorded for apex-promise-transport-commitizen →

Share this vulnerability

FAQ

It is an npm package that helps developers manage promise transport in commitizen environments.

The malicious code was identified by Amazon Inspector during a routine security assessment.

Using this package can lead to security vulnerabilities, including unauthorized access and potential data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Remove the package from your project immediately and look for alternative solutions until a secure version is released.

How To Fix

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

npm uninstall apex-promise-transport-commitizen

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