Which versions of getcardslib are malicious?

The following npm versions of getcardslib are flagged malicious: 1.0.0, 1.0.1, 1.0.2-beta, 1.0.3, 1.0.3-beta, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.9. Treat any of these as compromised.

How do I remediate getcardslib if I installed it?

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

If getcardslib was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is getcardslib part of a known attack campaign?

Yes — getcardslib is associated with the GHSA-4xvr-7wr9-qrcg 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 getcardslib across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for getcardslib (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getcardslib across your stack and pipelines.

Malicious package

getcardslibnpm

Malicious code in getcardslib (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2626

Immediate action

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

npm uninstall getcardslib

What this malware does

The package getcardslib was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

10 flagged

1.0.01.0.11.0.2-beta1.0.31.0.3-beta1.0.41.0.51.0.61.0.71.0.9

Indicators of compromise (SHA-256)

ce7e3143ce06f31e15162fef48924c625caddc3e6cc75c9640b053c38ad2665c

88c984b34b3bacb405ca57d999a20be2a2c4c1b3ad75fa7e60f8d6e814b30ab5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for getcardslib (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging getcardslib across your stack and pipelines.
If you installed it — respond
Remove getcardslib 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 getcardslib was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks getcardslib before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. getcardslib on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2-beta, 1.0.3, 1.0.3-beta, 1.0.4, 1.0.5, 1.0.6, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4xvr-7wr9-qrcg

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

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