Malicious Code Vulnerability in acme-diagnostics Package

acme-diagnostics Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6396: Malicious code in acme-diagnostics (npm). Affects acme-diagnostics versions 1.0.0 – 1.0.1. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The acme-diagnostics package is a Node.js library designed for diagnostic purposes, providing tools for analyzing and troubleshooting various aspects of applications. It is widely used in the npm ecosystem due to its ease of integration and functionality. However, recent findings have revealed that certain versions of this package contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability identified in the acme-diagnostics package stems from the inclusion of malicious code in versions 1.0.0 and 1.0.1. This code can potentially compromise the integrity of applications using this package, leading to unauthorized access, data breaches, or other malicious activities. The issue was reported by ReversingLabs and is cataloged under multiple identifiers, including GHSA-hrpj-x9hr-gg9j and SNYK-JS-ACMEDIAGNOSTICS-10558303.

How To Fix

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

npm uninstall acme-diagnostics

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

If immediate updating is not feasible, consider temporarily removing the acme-diagnostics package from your project until a secure version is available. This can be done using the command: npm uninstall acme-diagnostics.

Conclusion

The acme-diagnostics package has been found to contain malicious code in specific versions, posing a serious security threat to users. It is crucial to update to a secure version or remove the package until a fix is available. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for acme-diagnostics →

Share this vulnerability

FAQ

Versions 1.0.0 and 1.0.1 of the acme-diagnostics package are affected by the malicious code vulnerability.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you cannot update the package right away, consider uninstalling it temporarily to mitigate risks until a secure version is available.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat detection and analysis.

Using the affected package can lead to unauthorized access, data breaches, and other malicious activities that compromise the security of your application.

How To Fix

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

npm uninstall acme-diagnostics

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