Malicious Code Detected in beta-decompress-daemon-minify-simple Package

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15611: Malicious code in beta-decompress-daemon-minify-simple (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 beta-decompress-daemon-minify-simple package is an npm module designed for decompressing and minifying files. It is often used in web development to optimize file sizes and improve loading times. However, this package has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the beta-decompress-daemon-minify-simple package. This code can potentially compromise the security of applications that depend on this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall beta-decompress-daemon-minify-simple

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 beta-decompress-daemon-minify-simple package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The beta-decompress-daemon-minify-simple package has been identified as containing malicious code, which poses a significant threat to applications using it. Immediate action is required to remove the package and seek alternatives. Regular monitoring of dependencies is essential to maintain application security.

See every vulnerability recorded for beta-decompress-daemon-minify-simple →

Share this vulnerability

FAQ

It is an npm module used for decompressing and minifying files in web development.

The specific nature of the malicious code has not been disclosed, but it poses a risk of unauthorized access and data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Remove the package from your project and look for alternative solutions. If a patched version is released, update accordingly.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.

How To Fix

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

npm uninstall beta-decompress-daemon-minify-simple

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