Which versions of gemini-ai-checker are malicious?

The following npm versions of gemini-ai-checker are flagged malicious: 1.3.3. Treat any of these as compromised.

How do I remediate gemini-ai-checker if I installed it?

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

If gemini-ai-checker 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 gemini-ai-checker part of a known attack campaign?

Yes — gemini-ai-checker is associated with the RLMA-2026-01952 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 gemini-ai-checker across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gemini-ai-checker (version 1.3.3).

Malicious package

gemini-ai-checkernpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

gemini-ai-checker is a confirmed malicious npm package (MAL-2026-2763) that executes malicious code on install (malicious version 1.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gemini-ai-checker (npm)

MAL-2026-2763

Immediate action

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

npm uninstall gemini-ai-checker

What this malware does

The package gemini-ai-checker was found to contain malicious code.

Malicious versions

1 flagged

1.3.3

Indicators of compromise (SHA-256)

04f2490d04012e88da610af17f000efa0e2f2edcb9b167b64f35da7d6658c3e0

ce523af945a4246ec60ceb49c42757844915ea6b3657e989e0254ae1212aab92

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01952

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks gemini-ai-checker-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