Which versions of pkg1bate5apg1 are malicious?

The following npm versions of pkg1bate5apg1 are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate pkg1bate5apg1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for pkg1bate5apg1 (version 99.99.99).

Malicious package

pkg1bate5apg1npm

Advisory published Jan 2, 2026Updated Mar 19, 2026

pkg1bate5apg1 is a confirmed malicious npm package (MAL-2026-22) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pkg1bate5apg1 (npm)

MAL-2026-22

Immediate action

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

npm uninstall pkg1bate5apg1

What this malware does

The package pkg1bate5apg1 was found to contain malicious code.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

c85b2d2c9cdcf5df7190e4771a4438616bc6f487b2f99d90f7de10346618886d

81f618c8672f75f3c38a3a09e706a8d024965fdd62ce97bad8246dab443d2ebf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01492

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks pkg1bate5apg1-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