Which versions of @rbapp/pages are malicious?

The following npm versions of @rbapp/pages are flagged malicious: 2.2.2. Treat any of these as compromised.

How do I remediate @rbapp/pages if I installed it?

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

If @rbapp/pages 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 @rbapp/pages part of a known attack campaign?

Yes — @rbapp/pages is associated with the RLMA-2025-04873 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 @rbapp/pages across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @rbapp/pages (version 2.2.2).

Part of a larger attack: @rbapp published 9 malicious packages. See the full campaign →

Malicious package

@rbapp/pagesnpm

Advisory published Aug 28, 2025Updated Sep 26, 2025

@rbapp/pages is a confirmed malicious npm package (MAL-2025-41930) that executes malicious code on install (malicious version 2.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @rbapp/pages (npm)

MAL-2025-41930

Immediate action

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

npm uninstall @rbapp/pages

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

2.2.2

Indicators of compromise (SHA-256)

fdc1c31c0775a5ffe1699ac33a0c69128bab1f2a86621309e852702491726676

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-04873

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @rbapp/pages-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