Which versions of rtxaspnet are malicious?

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

How do I remediate rtxaspnet if I installed it?

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

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

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

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

Malicious package

rtxaspnetnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

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

MAL-2026-2799

Immediate action

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

npm uninstall rtxaspnet

What this malware does

The package rtxaspnet was found to contain malicious code.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3abab5515174200f827a76d31f3984dda1179cbc412a2a6fc65cbef1b907a2f8

090604cfa202f9f464d120e8fe6ce4a731ca1011e78d84cf715894ec79e1b3c1

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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