Critical Malicious Code Vulnerability in @hrmony/devtool-configuration Package

Summary

29/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17260: Malicious code in @hrmony/devtool-configuration (npm). Affects @hrmony/devtool-configuration versions 1.99.0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @hrmony/devtool-configuration package is an npm module designed for development tool configuration management. It is used to streamline the setup and configuration of various development tools in JavaScript projects. However, this package has been found to contain malicious code that compromises the security of systems where it is installed.

Vulnerability Detail

The vulnerability originates from the package's index.js file, which performs an unconditional POST request to an external server upon import. This request sends sensitive information, including AWS EC2 instance metadata, IAM security credentials, and environment variables, to an attacker-controlled host. The malicious code executes without any user consent, leading to a complete compromise of the affected system. Users should consider any system with this package installed as fully compromised.

How To Fix

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

npm uninstall @hrmony/devtool-configuration

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

There are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely.

Conclusion

The @hrmony/devtool-configuration package contains a critical vulnerability that allows malicious actors to collect sensitive information from affected systems. Immediate action is required to remove the package and secure any exposed credentials. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @hrmony/devtool-configuration →

Share this vulnerability

FAQ

Immediately uninstall the @hrmony/devtool-configuration package and rotate any secrets or keys that may have been exposed.

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

Leaving this package installed can lead to unauthorized access to sensitive information, including AWS credentials and environment variables, potentially compromising your entire system.

After removing the package, ensure that you rotate all credentials and secrets that may have been exposed. Monitor your systems for any unusual activity.

This vulnerability can lead to a complete compromise of your development environment, allowing attackers to gain access to sensitive data and potentially control your systems.

How To Fix

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

npm uninstall @hrmony/devtool-configuration

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