Which versions of @hrmony/belegerfassung-pladddform are malicious?

The following npm versions of @hrmony/belegerfassung-pladddform are flagged malicious: 1.99.0. Treat any of these as compromised.

How do I remediate @hrmony/belegerfassung-pladddform if I installed it?

@hrmony/belegerfassung-pladddform is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @hrmony/belegerfassung-pladddform — how do I know if it already compromised me?

If @hrmony/belegerfassung-pladddform was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @hrmony/belegerfassung-pladddform part of a known attack campaign?

Yes — @hrmony/belegerfassung-pladddform is associated with the IN-MAL-2026-020638 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @hrmony/belegerfassung-pladddform across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/belegerfassung-pladddform (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/belegerfassung-pladddform across your stack and pipelines.

Malicious package

@hrmony/belegerfassung-pladddformnpm

@hrmony/belegerfassung-pladddform is a confirmed malicious npm package (MAL-2026-17252) that steals credentials and exfiltrates sensitive data (malicious version 1.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @hrmony/belegerfassung-pladddform (npm)

MAL-2026-17252

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @hrmony/belegerfassung-pladddform

What this malware does

The package's main module (index.js) executes exfiltration logic at top level on import. It first sends a hello beacon via HTTP POST to the hardcoded endpoint https://hrnmn.dd.h4x.tv/save_instance_info_from_pkge_hrmony_belegerfassung-pladddform, then queries the AWS EC2 Instance Metadata Service at 169.254.169.254 using IMDSv2 to enumerate ami-id, instance identity, IAM role names, and their security-credentials (including short-lived ec2-instance credentials and user-data), and POSTs the harvested object to the same endpoint. It also enumerates every entry of process.env and recursively reads all files under /var/run/secrets/ (the Kubernetes service-account and secret mount point), then POSTs the combined payload to the same endpoint. The package name uses a typosquat pattern (belegerfassung-pladddform with duplicated letters under the @hrmony scope resembling @harmony) and declares an unpinned dependency @hrmony/kit-5 (^1.0.0) on the same attacker-controlled scope, extending the payload delivery surface via a transitive dependency.

Malicious versions

1 flagged

1.99.0

Indicators of compromise (SHA-256)

615255a66c44204b03e60a165c1a9b21f95ecd351bf58c355462c159c74d1017

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hrmony/belegerfassung-pladddform (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hrmony/belegerfassung-pladddform across your stack and pipelines.
If you installed it — respond
@hrmony/belegerfassung-pladddform is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @hrmony/belegerfassung-pladddform was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @hrmony/belegerfassung-pladddform before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @hrmony/belegerfassung-pladddform on npm has been identified as a malicious package (version 1.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020638

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @hrmony/belegerfassung-pladddform-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database