Which versions of @digitalpharmacist/http-error-util are malicious?

The following npm versions of @digitalpharmacist/http-error-util are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @digitalpharmacist/http-error-util if I installed it?

Remove @digitalpharmacist/http-error-util 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 @digitalpharmacist/http-error-util — how do I know if it already compromised me?

If @digitalpharmacist/http-error-util 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 @digitalpharmacist/http-error-util part of a known attack campaign?

Yes — @digitalpharmacist/http-error-util is associated with the GHSA-jw9w-w49g-cx4h, RLMA-2026-04712, RLUA-2026-05410 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 @digitalpharmacist/http-error-util across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @digitalpharmacist/http-error-util (version 99.9.1).

Malicious package

@digitalpharmacist/http-error-utilnpm

Advisory published Jun 29, 2026Updated Jul 23, 2026

@digitalpharmacist/http-error-util is a confirmed malicious npm package (MAL-2026-6615) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @digitalpharmacist/http-error-util (npm)

MAL-2026-6615

Immediate action

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

npm uninstall @digitalpharmacist/http-error-util

What this malware does

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

99.9.1

Indicators of compromise (SHA-256)

bd3874246d23d6027bd09962515c8e79a0246740ff5fc6f853270c0a40271d18

45b583578d88c0efad590c03d951cbae95e1aca95450d1830b46cd305cfefabc

8666fa7be246311ffff906d68af4d7a04c2448da6f9284d3f322f5d340c81e76

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @digitalpharmacist/http-error-util (version 99.9.1).
If you installed it — respond
Remove @digitalpharmacist/http-error-util 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 @digitalpharmacist/http-error-util 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. @digitalpharmacist/http-error-util on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jw9w-w49g-cx4hRLMA-2026-04712RLUA-2026-05410

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @digitalpharmacist/http-error-util-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