Critical Malicious Code Vulnerability in comment-on-task-github-action Package

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5768: Malicious code in comment-on-task-github-action (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 comment-on-task-github-action package is an npm module designed to facilitate automated comments on GitHub tasks. It is commonly used in CI/CD pipelines to enhance collaboration and communication among development teams. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, posing significant risks to sensitive data and system integrity.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the comment-on-task-github-action package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall comment-on-task-github-action

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

Currently, the best workaround is to uninstall the comment-on-task-github-action package completely. You can do this by running the following command in your terminal: npm uninstall comment-on-task-github-action. Additionally, monitor your systems for any unusual activity following the uninstallation.

Conclusion

The comment-on-task-github-action package contains malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Utilize tools like Vulert to monitor for vulnerabilities in your applications and maintain best practices for dependency management.

See every vulnerability recorded for comment-on-task-github-action →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on the affected system.

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

Keeping this package installed can lead to unauthorized access to sensitive data and potential data breaches.

As of now, there is no patched version available. The recommended action is to uninstall the package.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.

How To Fix

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

npm uninstall comment-on-task-github-action

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