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

The following npm versions of @athena-ui-components/graceful-degradation are flagged malicious: 1.1.26, 1.1.27. Treat any of these as compromised.

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

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

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

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

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

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

Malicious package

@athena-ui-components/graceful-degradationnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@athena-ui-components/graceful-degradation is a confirmed malicious npm package (MAL-2026-7042) that executes malicious code on install (malicious versions 1.1.26, 1.1.27). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-7042

Immediate action

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

npm uninstall @athena-ui-components/graceful-degradation

Malicious versions

2 flagged

1.1.261.1.27

Indicators of compromise (SHA-256)

b9bd98a621c695bb55a4b881db56e3771a74f817ec775cc58671fe1e7ea7edf6

35ab22ff7aa9975547ea118d6fa1bdca7bac32e26e4414340ac32bd27d24cc6f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04674RLUA-2026-05814

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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