Critical Malicious Code Vulnerability in boogeyman Package

boogeyman Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15955: Malicious code in boogeyman (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 boogeyman package is an npm library designed to provide various functionalities for developers, including utilities for managing asynchronous operations and handling errors. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package. The vulnerability affects all versions starting from its introduction, making it imperative for users to take immediate action.

Vulnerability Detail

The vulnerability in the boogeyman package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or even complete system takeover. The malicious nature of the code was discovered by Amazon Inspector, highlighting the need for vigilance when using third-party packages in software development.

How To Fix

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

npm uninstall boogeyman

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 replacing the boogeyman package with alternative libraries that provide similar functionalities without the associated risks. Review your project's dependencies and ensure that no other vulnerable packages are included.

Conclusion

The discovery of malicious code in the boogeyman package underscores the importance of regularly auditing dependencies in software projects. Users are strongly advised to remove the affected package and monitor for updates or patches to ensure the security of their applications.

See every vulnerability recorded for boogeyman →

Share this vulnerability

FAQ

The boogeyman package is an npm library that offers various utilities for developers, particularly for managing asynchronous operations.

The malicious code was identified by Amazon Inspector, a security tool that scans for vulnerabilities in open-source packages.

The risks include unauthorized access to sensitive data, potential data breaches, and the possibility of a complete system compromise.

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.

If immediate removal is not possible, look for alternative packages that provide similar functionality and consider implementing additional security measures.

Related vulnerabilities

Recent vulnerabilities recorded for boogeyman.

How To Fix

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

npm uninstall boogeyman

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