Which versions of @atlaskit-internal_.smart-card/hover-card are malicious?

The following npm versions of @atlaskit-internal_.smart-card/hover-card are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @atlaskit-internal_.smart-card/hover-card if I installed it?

Remove @atlaskit-internal_.smart-card/hover-card 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 @atlaskit-internal_.smart-card/hover-card — how do I know if it already compromised me?

If @atlaskit-internal_.smart-card/hover-card 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 @atlaskit-internal_.smart-card/hover-card part of a known attack campaign?

Yes — @atlaskit-internal_.smart-card/hover-card is associated with the RLMA-2026-05400, RLUA-2026-05822 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 @atlaskit-internal_.smart-card/hover-card across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @atlaskit-internal_.smart-card/hover-card (version 99.0.0).

Malicious package

@atlaskit-internal_.smart-card/hover-cardnpm

Advisory published Jul 20, 2026Updated Sep 1, 2026

@atlaskit-internal_.smart-card/hover-card is a confirmed malicious npm package (MAL-2026-10870) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @atlaskit-internal_.smart-card/hover-card (npm)

MAL-2026-10870

Immediate action

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

npm uninstall @atlaskit-internal_.smart-card/hover-card

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

39a49f2e2132acbd350cfd1a31f5299ebeb43a80b5fb4e25638d8c664dc88845

8850ed85c3150acc7847e44a995f8d30f308f2ec81f547f7dff5f8b4ba925342

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05400RLUA-2026-05822

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @atlaskit-internal_.smart-card/hover-card-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