Malicious Code Detected in boolean-theta-static-sudo-node Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15964: Malicious code in boolean-theta-static-sudo-node (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 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 boolean-theta-static-sudo-node package is an npm library designed for specific boolean operations in Node.js applications. It is utilized for its simplicity and efficiency in handling boolean logic. However, this package has been found to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the boolean-theta-static-sudo-node package. This code can potentially compromise the security of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The issue affects all versions starting from 0, making it critical for users to take immediate action.

How To Fix

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

npm uninstall boolean-theta-static-sudo-node

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 workaround, you can avoid using the boolean-theta-static-sudo-node package and look for alternative libraries that provide similar functionality without the associated risks.

Conclusion

The boolean-theta-static-sudo-node package has been identified as containing malicious code, posing a serious security threat to applications. Users are advised to uninstall the package and monitor their projects for vulnerabilities using tools like Vulert.

See every vulnerability recorded for boolean-theta-static-sudo-node →

Share this vulnerability

FAQ

The malicious code is designed to exploit vulnerabilities in applications, potentially leading to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

You should immediately uninstall the package and consider using alternative libraries that do not pose security risks.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall boolean-theta-static-sudo-node

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