Critical Malicious Code Vulnerability in acidwater Package

acidwater Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14002: Malicious code in acidwater (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The acidwater package is an npm module designed for various functionalities, potentially including data manipulation or web interactions. However, it has been identified to contain malicious code that poses a significant security risk to users and their applications. This vulnerability can lead to unauthorized access or data breaches, making it crucial for developers to address it promptly.

Vulnerability Detail

The vulnerability in the acidwater package originates from the inclusion of malicious code within its codebase. This code can execute harmful actions without the user's consent, potentially compromising sensitive data or system integrity. The issue affects all versions starting from 0, making it imperative for users to take immediate action to mitigate risks associated with this vulnerability.

How To Fix

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

npm uninstall acidwater

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 replace the functionality provided by the acidwater package with alternative libraries that do not have known vulnerabilities. It is advisable to review the project dependencies and ensure that no other malicious packages are included.

Conclusion

The acidwater package has been identified to contain malicious code, posing a significant risk to users. It is essential to remove this package from your projects and seek alternatives until a secure version is released. Regular monitoring of dependencies using tools like Vulert can help maintain application security.

See every vulnerability recorded for acidwater →

Share this vulnerability

FAQ

The acidwater package is an npm module that provides various functionalities, but it has been found to contain malicious code.

The malicious code can execute harmful actions, potentially leading to unauthorized access to sensitive data or system breaches.

You should immediately remove the acidwater package from your project and look for alternative libraries.

Currently, there is no patched version available for the acidwater package. It is recommended to avoid using it until a secure version is released.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall acidwater

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