Which versions of @rbapp/i18n are malicious?

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

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

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

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

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

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

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

Malicious package

@rbapp/i18nnpm

Advisory published Aug 28, 2025Updated Sep 26, 2025

@rbapp/i18n is a confirmed malicious npm package (MAL-2025-41928) 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/i18n (npm)

MAL-2025-41928

Immediate action

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

npm uninstall @rbapp/i18n

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)

4824ed9480199ceb809aa00525fbe77a016ef3d11c9c680b7bf1db3f1f50fa17

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @rbapp/i18n (version 2.2.2).
If you installed it — respond
Remove @rbapp/i18n 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/i18n 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/i18n 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-04871

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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