Which versions of hrpdesign are malicious?

The following npm versions of hrpdesign are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate hrpdesign if I installed it?

Remove hrpdesign from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed hrpdesign — how do I know if it already compromised me?

If hrpdesign was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is hrpdesign part of a known attack campaign?

Yes — hrpdesign is associated with the GHSA-w9wg-x2hg-8c6q, RLMA-2025-05034, RLUA-2026-01344 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 hrpdesign across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hrpdesign (version 1.0.0).

Malicious package

hrpdesignnpm

Advisory published Sep 9, 2025Updated Mar 19, 2026

hrpdesign is a confirmed malicious npm package (MAL-2025-47063) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hrpdesign (npm)

MAL-2025-47063

Immediate action

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

npm uninstall hrpdesign

What this malware does

The package communicates with a domain associated with malicious activity.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e370e366167f90ff8c5a3a171abe2bb14e301cdd2d5499e98f66bd1e653fcf88

c03563accd5433822abdd1392aa9bd1309306d352ba0372f491213a60d975371

49e23956fee1f65ca8e4832ee6b88aba6a50696805a6fcc210e958303f592c72

581a4af1b81af48701a737f68e5d2839f747153c4c776dd3e8f1ba1e8f97a26b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hrpdesign (version 1.0.0).
If you installed it — respond
Remove hrpdesign from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If hrpdesign was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. hrpdesign on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w9wg-x2hg-8c6qRLMA-2025-05034RLUA-2026-01344

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks hrpdesign-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database