Which versions of estaspnet are malicious?

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

How do I remediate estaspnet if I installed it?

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

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

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

Search your lockfiles and build artifacts for estaspnet (version 1.0.0).

Malicious package

estaspnetnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

estaspnet is a confirmed malicious npm package (MAL-2026-2758) 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 estaspnet (npm)

MAL-2026-2758

Immediate action

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

npm uninstall estaspnet

What this malware does

The package estaspnet was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f016a21141d6e26c63284ba9d307533df3a231ddea86c86ecadee629ff24bf6d

2c5d06cbbad43dc5b62ae0a9cd37980a791be8e0ba957a9a4f9f41285000732e

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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