Credential Harvesting Vulnerability in @hrmony/kit-4 Package

@hrmony/kit-4 Updated 29 Sep 2026

Summary

29/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17265: Malicious code in @hrmony/kit-4 (npm). Affects @hrmony/kit-4 versions 1.0.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/kit-4 package is an npm library designed for various functionalities within JavaScript applications. However, it has been identified to contain malicious code that poses significant security risks. This package executes credential-harvesting scripts during both installation and import, making it particularly dangerous for users operating in cloud environments such as AWS EC2 or Kubernetes.

Vulnerability Detail

The vulnerability originates from malicious code embedded in the @hrmony/kit-4 package. It runs credential-harvesting scripts that query the AWS EC2 instance metadata service to retrieve IAM role credentials and reads sensitive Kubernetes service-account tokens. This data is then sent to a hardcoded external server (hrnmn.dd.h4x.tv), exposing sensitive information to unauthorized parties. The vulnerability affects any environment where the package is installed or imported, leading to potential data breaches and unauthorized access to cloud resources.

How To Fix

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

npm uninstall @hrmony/kit-4

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, avoid using the @hrmony/kit-4 package in your applications. If you must use it, consider isolating it in a controlled environment where sensitive data is not accessible.

Conclusion

The @hrmony/kit-4 package contains serious vulnerabilities that can lead to credential theft and unauthorized access to sensitive information. It is crucial to remove this package from your projects and monitor your environments for any signs of compromise. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for @hrmony/kit-4 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that collects and transmits sensitive credentials to an external server.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Check your application against the vulnerability using the Vulert playground.

Immediately remove the @hrmony/kit-4 package from your project and monitor your environment for any unauthorized access.

As of now, there is no safe version available. It is recommended to avoid using this package until a secure version is released.

Vulert uses your package-lock.json to monitor and alert in real-time for open-source vulnerabilities, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall @hrmony/kit-4

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