Which versions of abstract-http-request are malicious?

The following npm versions of abstract-http-request are flagged malicious: 2.3.1, 99.99.1, 99.99.2. Treat any of these as compromised.

How do I remediate abstract-http-request if I installed it?

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

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

Yes — abstract-http-request is associated with the RLMA-2026-01084 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 abstract-http-request across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for abstract-http-request (3 malicious versions).

Malicious package

abstract-http-requestnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

abstract-http-request is a confirmed malicious npm package (MAL-2026-1646) that executes malicious code on install (malicious versions 2.3.1, 99.99.1, 99.99.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abstract-http-request (npm)

MAL-2026-1646

Immediate action

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

npm uninstall abstract-http-request

What this malware does

The package abstract-http-request was found to contain malicious code.

Malicious versions

3 flagged

2.3.199.99.199.99.2

Indicators of compromise (SHA-256)

fcdceb9c85622b9da0199db50d64ac889afdf4f593ff980b650930d3ce4c4652

84130e04f5582700fd6841f67e465fb571518a710f3257fae0990653bf08aa92

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for abstract-http-request (3 malicious versions).
If you installed it — respond
Remove abstract-http-request 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 abstract-http-request 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. abstract-http-request on npm has been identified as a malicious package (versions 2.3.1, 99.99.1, 99.99.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01084

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks abstract-http-request-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