Critical Malicious Code Vulnerability in hubspot-cms-deploy Package

hubspot-cms-deploy Updated 02 Oct 2025

Summary

10/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5781: Malicious code in hubspot-cms-deploy (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 hubspot-cms-deploy package is an npm tool designed for deploying HubSpot CMS projects. It facilitates the management and deployment of assets, content, and configurations to HubSpot's platform. However, this package has been identified to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the hubspot-cms-deploy package. This code can lead to a complete compromise of the affected system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code poses significant risks, including data theft and unauthorized control over the affected machine.

How To Fix

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

npm uninstall hubspot-cms-deploy

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 workaround, you can temporarily disable the package in your project by removing it from your dependencies in package.json and running 'npm install' to update your lock file. However, this does not guarantee the removal of all malicious software that may have been installed.

Conclusion

The hubspot-cms-deploy package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring of dependencies is crucial to maintain the security of your applications.

See every vulnerability recorded for hubspot-cms-deploy →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any secrets or keys stored on the affected machine.

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

Currently, there is no patched version available. It is recommended to remove the package until a fix is released.

Failure to address this vulnerability can lead to unauthorized access to sensitive data and complete control over your system by malicious actors.

While many npm packages are safe, it is essential to regularly monitor your dependencies for vulnerabilities and use tools like Vulert to stay informed.

How To Fix

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

npm uninstall hubspot-cms-deploy

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