Critical Malicious Code Vulnerability in acghrom Package

acghrom Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-13994: Malicious code in acghrom (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The acghrom package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various tasks, but its integrity has been compromised due to the presence of malicious code. This vulnerability poses significant risks to users who rely on this package for their projects.

Vulnerability Detail

The acghrom package has been identified to contain malicious code that can lead to unauthorized access, data breaches, or other harmful actions within the applications that utilize it. This vulnerability originated from the introduction of malicious elements in the package, making it a severe threat to developers and users alike. The implications of this vulnerability can range from data theft to complete system compromise, depending on how the package is integrated into applications.

How To Fix

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

npm uninstall acghrom

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 an immediate update is not feasible, consider removing the acghrom package from your project and replacing it with an alternative library that offers similar functionality without the associated risks.

Conclusion

The acghrom package has been found to contain malicious code, posing significant risks to users and their applications. It is crucial to update the package to a secure version or find an alternative to mitigate these risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for acghrom →

Share this vulnerability

FAQ

The acghrom package is an npm library used in JavaScript applications for various functionalities.

The malicious code was introduced in the package, compromising its integrity and posing risks to users.

Using the acghrom package can lead to unauthorized access, data breaches, and other harmful actions within applications.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If an immediate update is not possible, consider removing the acghrom package and replacing it with a safer alternative.

How To Fix

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

npm uninstall acghrom

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