Which versions of hiro-docs are malicious?

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

How do I remediate hiro-docs if I installed it?

Remove hiro-docs 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 hiro-docs — how do I know if it already compromised me?

If hiro-docs 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 hiro-docs part of a known attack campaign?

Yes — hiro-docs is associated with the RLMA-2025-06363 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 hiro-docs across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hiro-docs (version 1.0.0).

Malicious package

hiro-docsnpm

Advisory published Dec 23, 2025Updated Dec 24, 2025

hiro-docs is a confirmed malicious npm package (MAL-2025-192801) 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 hiro-docs (npm)

MAL-2025-192801

Immediate action

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

npm uninstall hiro-docs

What this malware does

The package hiro-docs was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

194711f5dd27675c678e89915744bdfc791583da456fcef70cc1511e7f40fd83

88d9fa34d301fc54a2088114411b7016fb25c8f3b581c52f9e0613b103edda15

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for hiro-docs (version 1.0.0).
If you installed it — respond
Remove hiro-docs 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 hiro-docs 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. hiro-docs 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

RLMA-2025-06363

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks hiro-docs-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