Which versions of llm-oracle are malicious?

The following npm versions of llm-oracle are flagged malicious: 0.0.1-security, 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate llm-oracle if I installed it?

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

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

Yes — llm-oracle is associated with the GHSA-84fm-x46g-jqx9, RLMA-2026-01422, RLUA-2026-01782, RLUA-2026-01986 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 llm-oracle 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 llm-oracle (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llm-oracle across your stack and pipelines.

Malicious package

llm-oraclenpm

Malicious code in llm-oracle (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1331

Immediate action

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

npm uninstall llm-oracle

What this malware does

The package llm-oracle 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

4 flagged

0.0.1-security1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

94a20da2ad0a043d47545889257036cffa168646e3083c39007db16c692dc419

4f0e3feea4f9a606a80b59a1ba8d091e54370c3c5d7264dc79f3d5494b21b421

98fdc3b2f8d6e1b4bb0e26b6f7f12227b5759900fb7c859b6b13093b1a159bf9

b0d7d04cf1c90d0ac203d8528f2693db560dadff75e5fe9e2c07f193313f1942

55738498cc5c0d3d7c5e1d87efc4059174584c02ec97eec77ad8b4efd37c8ee4

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 llm-oracle (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging llm-oracle across your stack and pipelines.
If you installed it — respond
Remove llm-oracle 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 llm-oracle 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 llm-oracle 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. llm-oracle on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-84fm-x46g-jqx9RLMA-2026-01422RLUA-2026-01782RLUA-2026-01986

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks llm-oracle-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