Which versions of @athena-ui-components/pubsub-bridge are malicious?

The following npm versions of @athena-ui-components/pubsub-bridge are flagged malicious: 0.0.16, 0.0.17. Treat any of these as compromised.

How do I remediate @athena-ui-components/pubsub-bridge if I installed it?

Remove @athena-ui-components/pubsub-bridge 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 @athena-ui-components/pubsub-bridge — how do I know if it already compromised me?

If @athena-ui-components/pubsub-bridge 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 @athena-ui-components/pubsub-bridge part of a known attack campaign?

Yes — @athena-ui-components/pubsub-bridge is associated with the RLMA-2026-04679, RLUA-2026-05819 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 @athena-ui-components/pubsub-bridge across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @athena-ui-components/pubsub-bridge (2 malicious versions).

Part of a larger attack: @athena-ui-components published 11 malicious packages. See the full campaign →

Malicious package

@athena-ui-components/pubsub-bridgenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@athena-ui-components/pubsub-bridge is a confirmed malicious npm package (MAL-2026-7047) that executes malicious code on install (malicious versions 0.0.16, 0.0.17). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @athena-ui-components/pubsub-bridge (npm)

MAL-2026-7047

Immediate action

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

npm uninstall @athena-ui-components/pubsub-bridge

Malicious versions

2 flagged

0.0.160.0.17

Indicators of compromise (SHA-256)

4f62cd6a92c4f9e5c071959f89b1a3510652aafc57cd87e4e06d00e86713a84e

f25be3aff0d8e797f736b5140b5536cc373678135c492f8bc46badb068be1816

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04679RLUA-2026-05819

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @athena-ui-components/pubsub-bridge-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