Critical Malicious Code Vulnerability in @hrmony/interfaces Package

@hrmony/interfaces Updated 29 Sep 2026

Summary

29/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17262: Malicious code in @hrmony/interfaces (npm). Affects @hrmony/interfaces versions 0.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 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 @hrmony/interfaces package is an npm library designed for internal use, which has been found to contain malicious code. This package is intended for managing interfaces in applications but has been compromised, leading to severe security risks for any system that installs it. The malicious code executes upon import, making it particularly dangerous.

Vulnerability Detail

The vulnerability originates from the package's index.js file, which executes top-level asynchronous code on any require or import of the package. This code retrieves sensitive AWS IMDSv2 tokens, EC2 instance identity, IAM role temporary security credentials, user data, and network metadata. It also serializes the entire process environment and reads Kubernetes secrets, ultimately exfiltrating this information to a hardcoded endpoint. The ramifications include unauthorized access to AWS resources, CI/CD pipelines, and sensitive data, effectively compromising any system that has the package installed.

How To Fix

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

npm uninstall @hrmony/interfaces

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 workaround, you can isolate the affected application from the network to prevent data exfiltration while you remove the package. Additionally, consider using environment variable management tools to secure sensitive information.

Conclusion

The @hrmony/interfaces package contains a critical vulnerability that can lead to severe security breaches. Immediate action is required to remove the package and secure any exposed credentials. Utilizing tools like Vulert can help in monitoring and preventing such vulnerabilities in the future.

See every vulnerability recorded for @hrmony/interfaces →

Share this vulnerability

FAQ

You should remove the package immediately and rotate any credentials or secrets that may have been exposed.

You can use Vulert to monitor and alert for open-source vulnerabilities in your application. Visit Vulert Scanner to check your application without needing to sign up.

Leaving this package installed can lead to unauthorized access to your AWS resources, sensitive data exposure, and potential control over your system by malicious actors.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure to follow best practices for package management.

If immediate removal is not possible, isolate the application from the network to mitigate the risk of data exfiltration.

How To Fix

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

npm uninstall @hrmony/interfaces

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