Which versions of uba-plugins are malicious?

The following npm versions of uba-plugins are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate uba-plugins if I installed it?

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

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

Yes — uba-plugins is associated with the GHSA-qg89-j3ph-h5cc, RLMA-2026-01629 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 uba-plugins 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 uba-plugins (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uba-plugins across your stack and pipelines.

Malicious package

uba-pluginsnpm

Malicious code in uba-plugins (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192567

Immediate action

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

npm uninstall uba-plugins

What this malware does

The package uba-plugins was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

2a73b282a96cbf09b981101e3b9e4056c51c7d9524e1cf62a41d71ce8f90f36f

bcb257605c151aafe2aad5cfe0a574b33989c084ccee06ee6ff0b74c33afb907

7cf84d614819711564557d2785b0d128ca539bf3f01735569df1a103015b43d3

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 uba-plugins (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging uba-plugins across your stack and pipelines.
If you installed it — respond
Remove uba-plugins 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 uba-plugins 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 uba-plugins 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. uba-plugins on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qg89-j3ph-h5ccRLMA-2026-01629

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks uba-plugins-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