Which versions of loyalty-card are malicious?

The following npm versions of loyalty-card are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate loyalty-card if I installed it?

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

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

Yes — loyalty-card is associated with the RLMA-2026-01423 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 loyalty-card across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for loyalty-card (version 100.0.0).

Malicious package

loyalty-cardnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

loyalty-card is a confirmed malicious npm package (MAL-2026-1789) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in loyalty-card (npm)

MAL-2026-1789

Immediate action

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

npm uninstall loyalty-card

What this malware does

The package loyalty-card was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

782405d14451aae6d4b09a1a8ff1f522f439e7741ee19ad1252c04e1c4286c2e

ae7127001e7050600c6ccf6afcc74aa672cb2fed26f21f1f25145c9027ac7f9f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01423

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks loyalty-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