Which versions of rce-pkg-1 are malicious?

The following npm versions of rce-pkg-1 are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate rce-pkg-1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for rce-pkg-1 (2 malicious versions).

Malicious package

rce-pkg-1npm

Advisory published Mar 18, 2026Updated Mar 23, 2026

rce-pkg-1 is a confirmed malicious npm package (MAL-2026-1833) that executes malicious code on install (malicious versions 1.0.0, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rce-pkg-1 (npm)

MAL-2026-1833

Immediate action

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

npm uninstall rce-pkg-1

What this malware does

The package rce-pkg-1 was found to contain malicious code.

Malicious versions

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

63e13fc42a58e54d7d2d6d7b2fe38afbae439df222e1457e6cba1fbca35e3755

00722c1eda950154ab61163515f1ee91bd18cd2be33793e0bf446884abc30771

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for rce-pkg-1 (2 malicious versions).
If you installed it — respond
Remove rce-pkg-1 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 rce-pkg-1 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. rce-pkg-1 on npm has been identified as a malicious package (versions 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01520

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks rce-pkg-1-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