Malicious Code Detected in fork-daemon-container-wind-boolean Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20781: Malicious code in fork-daemon-container-wind-boolean (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 fork-daemon-container-wind-boolean package is an npm module designed for managing daemon processes in containerized environments. It provides functionalities to facilitate the execution and management of background tasks within containers. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the fork-daemon-container-wind-boolean package. This code can potentially compromise the security of applications that depend on it, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.

How To Fix

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

npm uninstall fork-daemon-container-wind-boolean

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 workaround, consider using alternative packages that provide similar functionalities without the associated risks. Always ensure to review the security status of any package before integrating it into your project.

Conclusion

The fork-daemon-container-wind-boolean package has been identified to contain malicious code that poses serious security threats. Users are advised to uninstall the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for fork-daemon-container-wind-boolean →

Share this vulnerability

FAQ

It is an npm module used for managing daemon processes in containerized environments.

The specific nature of the malicious code has not been disclosed, but it poses significant security risks.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

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

You should uninstall the package immediately and consider using alternative solutions.

How To Fix

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

npm uninstall fork-daemon-container-wind-boolean

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