Critical Malicious Code Vulnerability in dewbrew Package

dewbrew Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18382: Malicious code in dewbrew (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 dewbrew package is an npm module designed for brewing and managing various types of beverages programmatically. It offers functionalities such as recipe management, ingredient tracking, and brewing process automation. However, it has been found to contain malicious code that poses significant security risks to users.

Vulnerability Detail

The vulnerability in the dewbrew package stems from the inclusion of malicious code that can compromise user systems. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate further attacks on the user's environment. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability immediately.

How To Fix

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

npm uninstall dewbrew

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, users can remove the dewbrew package from their project until a secure version is released. This can be done with the command: 'npm uninstall dewbrew'. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The dewbrew package has been identified as containing malicious code that poses serious security risks. Users are strongly encouraged to update or remove the package to protect their systems. Monitoring tools like Vulert can assist in identifying vulnerabilities in other packages as well.

See every vulnerability recorded for dewbrew →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to user data and execute harmful commands on the user's system.

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

As of now, there is no patched version available. Users are advised to monitor the package repository for updates.

If immediate removal is not possible, ensure that your application is running in a secure environment and monitor for any suspicious activity.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

npm uninstall dewbrew

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