Which versions of abrhide are malicious?

The following npm versions of abrhide are flagged malicious: 3.1.22. Treat any of these as compromised.

How do I remediate abrhide if I installed it?

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

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

Yes — abrhide is associated with the GHSA-qfhx-g3q3-qqhf, RLMA-2025-06053, RLUA-2026-01083 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 abrhide 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 abrhide (version 3.1.22). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abrhide across your stack and pipelines.

Malicious package

abrhidenpm

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

MAL-2025-192553

Immediate action

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

npm uninstall abrhide

What this malware does

The package abrhide 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

1 flagged

3.1.22

Indicators of compromise (SHA-256)

06ce2fae0c8baa7ffbe797fa1b7e090a96bcbc928e66921a8c8aa2dd788b276c

915c7fe51aff6bedb2be97556debe08a952d2389c97d427479beda9d5d9d3ca6

2333ee81a067edba58e98447a8dc86dd29ba0b9619c58b91465980ccc686ea23

31203927148c44c316f373377743125bf417427a7c55eb476cfe560d0c046ac4

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 abrhide (version 3.1.22). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abrhide across your stack and pipelines.
If you installed it — respond
Remove abrhide 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 abrhide 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 abrhide 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. abrhide on npm has been identified as a malicious package (version 3.1.22 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qfhx-g3q3-qqhfRLMA-2025-06053RLUA-2026-01083

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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