Malicious Code Detected in marcom-ac-console: npm Package Vulnerability

marcom-ac-console Updated 02 Oct 2025

Summary

17/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6209: Malicious code in marcom-ac-console (npm). Affects marcom-ac-console versions 1.0.1 – 1.0.5. 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 'marcom-ac-console' package is an npm library designed for managing marketing automation console functionalities. It is used by developers to integrate marketing tools into their applications. However, this package has been identified as malicious, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in 'marcom-ac-console' arises from its communication with a domain associated with malicious activities. This behavior can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The malicious nature of the package was identified by the OpenSSF Package Analysis project, which flagged versions 1.0.1 and 1.0.5 as harmful.

How To Fix

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

npm uninstall marcom-ac-console

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 removing the package from your project until a secure version is released. You can do this by running: npm uninstall marcom-ac-console.

Conclusion

The 'marcom-ac-console' package has been identified as malicious due to its communication with harmful domains. Users are advised to update or remove the package to protect their applications. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for marcom-ac-console →

Share this vulnerability

FAQ

The vulnerability involves the package communicating with a domain linked to malicious activities, which can compromise security.

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

As a temporary measure, you should uninstall the package to mitigate any risks until a secure version is available.

Currently, versions 1.0.1 and 1.0.5 are flagged as malicious. Always check the package repository for updates on safe versions.

Vulert uses the package-lock.json file to monitor for vulnerabilities in your open-source dependencies and provides real-time alerts.

How To Fix

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

npm uninstall marcom-ac-console

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