Which versions of @bpa-internal/bpa-auth are malicious?

The following npm versions of @bpa-internal/bpa-auth are flagged malicious: 99.99.98, 99.99.99. Treat any of these as compromised.

How do I remediate @bpa-internal/bpa-auth if I installed it?

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

If @bpa-internal/bpa-auth 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 @bpa-internal/bpa-auth part of a known attack campaign?

Yes — @bpa-internal/bpa-auth is associated with the RLMA-2026-05832 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 @bpa-internal/bpa-auth across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @bpa-internal/bpa-auth (2 malicious versions).

Malicious package

@bpa-internal/bpa-authnpm

Advisory published Aug 24, 2026Updated Sep 1, 2026

@bpa-internal/bpa-auth is a confirmed malicious npm package (MAL-2026-15676) that executes malicious code on install (malicious versions 99.99.98, 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bpa-internal/bpa-auth (npm)

MAL-2026-15676

Immediate action

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

npm uninstall @bpa-internal/bpa-auth

Malicious versions

2 flagged

99.99.9899.99.99

Indicators of compromise (SHA-256)

b647920aa3c1c7b14c053049c17c70c1698f5812c5f134396631ba8972f84541

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05832

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @bpa-internal/bpa-auth-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