Critical Malicious Code Vulnerability in task-bots Package

task-bots Updated 02 Oct 2025

Summary

17/04/2025
CRITICAL
No i
Critical
Not published

MAL-2025-3263: Malicious code in task-bots (npm). Affects task-bots versions 1.0.0. 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 task-bots package is a Node.js library designed to facilitate the automation of tasks within various applications. It allows developers to create bots that can perform repetitive tasks efficiently. However, this package has been identified as containing malicious code, which poses a significant security risk to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code in the task-bots package, as reported by the GitHub Security Advisory. Any system with this package installed is considered fully compromised, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious code can lead to severe ramifications, including 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 task-bots

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

There are no effective workarounds for this vulnerability other than removing the package and securing your system. Ensure that you monitor your environment for any signs of compromise.

Conclusion

The task-bots package has been compromised with malicious code, posing a serious threat to any system using it. Immediate action is required to remove the package and secure your environment. Utilize tools like Vulert to monitor for vulnerabilities and ensure your applications remain secure.

See every vulnerability recorded for task-bots →

Share this vulnerability

FAQ

Immediately remove the task-bots package and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential control over your system by malicious actors.

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

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall task-bots

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