Which versions of hiagentxhjrce are malicious?

Every published version of hiagentxhjrce on npm is considered malicious. Remove the package entirely.

How do I remediate hiagentxhjrce if I installed it?

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

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

Yes — hiagentxhjrce is associated with the GHSA-rq46-v367-269c 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 hiagentxhjrce 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 hiagentxhjrce (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hiagentxhjrce across your stack and pipelines.

Malicious package

hiagentxhjrcenpm

Malicious code in hiagentxhjrce (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-532

Immediate action

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

npm uninstall hiagentxhjrce

What this malware does

The package hiagentxhjrce was found to contain malicious code.

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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

7af113818c5ee2d7a62e4e6d33e5f888b26b9825386ede2258a14fb8865d3803

b8fa906e5f60fbdf339efd2cb500d14956bc4a05e0e45bc268a9020163324862

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for hiagentxhjrce (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging hiagentxhjrce across your stack and pipelines.
If you installed it — respond
Remove hiagentxhjrce 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 hiagentxhjrce 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 hiagentxhjrce 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. hiagentxhjrce on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rq46-v367-269c

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks hiagentxhjrce-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