Malicious Code Detected in adcm-web2 Package - Security Alert

adcm-web2 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14068: Malicious code in adcm-web2 (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 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 adcm-web2 package is a Node.js library used for web development, providing various functionalities to enhance web applications. However, it has been identified to contain malicious code, posing significant risks to users and their applications. This vulnerability can lead to unauthorized access, data breaches, and other security threats.

Vulnerability Detail

The vulnerability in the adcm-web2 package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. The malicious code can execute harmful actions without the user's consent, potentially leading to data theft or system compromise. It is crucial for developers to be aware of this vulnerability to protect their applications from exploitation.

How To Fix

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

npm uninstall adcm-web2

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

Conclusion

The discovery of malicious code in the adcm-web2 package highlights the importance of maintaining secure coding practices and regularly updating dependencies. Users are urged to take immediate action to mitigate risks associated with this vulnerability.

See every vulnerability recorded for adcm-web2 →

Share this vulnerability

FAQ

adcm-web2 is a Node.js library designed for web development, offering various features to enhance web applications.

The malicious code was identified through security audits and reports from tools like Amazon Inspector.

Using the compromised adcm-web2 package can lead to unauthorized access, data breaches, and potential exploitation of your application.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. Visit https://vulert.com for more information.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall adcm-web2

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