Critical Malicious Code Vulnerability in todo-plz Package

todo-plz Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1533: Malicious code in todo-plz (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The todo-plz package is an npm library designed for managing to-do lists in JavaScript applications. It provides functionalities for adding, removing, and updating tasks. However, this package has been identified as containing malicious code, which poses a significant security risk to any system where it is installed.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the todo-plz package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The origin of this vulnerability is linked to the package being flagged as malicious by security researchers, indicating that any system running this package should be considered fully compromised.

How To Fix

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

npm uninstall todo-plz

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. It is crucial to monitor your system for any signs of compromise after removal.

Conclusion

The todo-plz package contains malicious code that poses a severe security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for vulnerabilities in the future.

See every vulnerability recorded for todo-plz →

Share this vulnerability

FAQ

You should immediately uninstall the todo-plz 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 your application without needing to sign up.

Keeping the todo-plz package installed can lead to unauthorized access to your system and potential data breaches, as the malicious code can compromise your entire machine.

After removing the package, you should rotate all secrets and keys and monitor your system for any unusual activity to ensure it is secure.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay informed about known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall todo-plz

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