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

The following npm versions of @athena-ui-components/hooks are flagged malicious: 0.2.13, 0.2.14. Treat any of these as compromised.

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

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

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

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

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

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

Malicious package

@athena-ui-components/hooksnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@athena-ui-components/hooks is a confirmed malicious npm package (MAL-2026-7044) that executes malicious code on install (malicious versions 0.2.13, 0.2.14). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-7044

Immediate action

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

npm uninstall @athena-ui-components/hooks

Malicious versions

2 flagged

0.2.130.2.14

Indicators of compromise (SHA-256)

912fff7cb2e0e2b12919068d4be74e1e7d1cfa1f08afe896b48df3d174dadbd1

225cd689e3f55e318332abefb61e5790f4febf5b772495738dc14bd1785a8244

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04676RLUA-2026-05816

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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