Which versions of @rbapp/constants are malicious?

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

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

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

If @rbapp/constants was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @rbapp/constants part of a known attack campaign?

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @rbapp/constants (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rbapp/constants across your stack and pipelines.

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

Malicious package

@rbapp/constantsnpm

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

MAL-2025-41926

Immediate action

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

npm uninstall @rbapp/constants

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)

becbbdbc0b2fb2e5eb894d9817b17e75f069121d3760d4635a5a1e8ee39dff14

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @rbapp/constants (version 2.2.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rbapp/constants across your stack and pipelines.
If you installed it — respond
Remove @rbapp/constants 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/constants was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @rbapp/constants before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @rbapp/constants 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-04869

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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