Malicious Code Detected in goodorbad Package - Security Alert

goodorbad Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21701: Malicious code in goodorbad (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The goodorbad package is an npm library designed to provide a simple interface for determining whether a given input is 'good' or 'bad'. It is commonly used in various applications for input validation and decision-making processes. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to users and their applications.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the goodorbad package. This code can potentially compromise the integrity of applications utilizing the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was identified in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate risks.

How To Fix

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

npm uninstall goodorbad

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, consider removing the goodorbad package from your project until a secure version is released. You can do this by executing the following command: npm uninstall goodorbad. Additionally, you may explore alternative packages that offer similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the goodorbad package highlights the importance of vigilance in open-source software usage. Users are urged to take immediate action by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help ensure ongoing security by providing real-time alerts for vulnerabilities.

See every vulnerability recorded for goodorbad →

Share this vulnerability

FAQ

The goodorbad package is an npm library that helps determine if a given input is 'good' or 'bad', often used for input validation.

The exact nature of the malicious code has not been disclosed, but it poses significant security risks, including unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

As of now, there is no patched version available. Users are advised to uninstall the package until a secure version is released.

It is recommended to uninstall the goodorbad package immediately and monitor for updates regarding a secure version. Consider using alternative packages in the meantime.

How To Fix

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

npm uninstall goodorbad

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