Which versions of @luminarycloudinternal/frodo are malicious?

The following npm versions of @luminarycloudinternal/frodo are flagged malicious: 9999.0.1, 9999.0.2, 9999.0.3. Treat any of these as compromised.

How do I remediate @luminarycloudinternal/frodo if I installed it?

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

If @luminarycloudinternal/frodo 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 @luminarycloudinternal/frodo part of a known attack campaign?

Yes — @luminarycloudinternal/frodo is associated with the IN-MAL-2026-008073, IN-MAL-2026-008124, GHSA-p92p-63h9-qrvc, IN-MAL-2026-009808 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 @luminarycloudinternal/frodo 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 @luminarycloudinternal/frodo (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @luminarycloudinternal/frodo across your stack and pipelines.

Malicious package

@luminarycloudinternal/frodonpm

Malicious code in @luminarycloudinternal/frodo (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6986

Immediate action

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

npm uninstall @luminarycloudinternal/frodo

What this malware does

Package published under a scope shadowing internal Luminary Cloud packages (@luminarycloudinternal) at version 9999.0.1 — the canonical dependency-confusion shape designed to win version resolution over a private internal package of the same name. On install, postinstall.js (line 8) performs an HTTPS GET to a hardcoded external host (poc-luminary-npm-1782987043.testingboxes.com) carrying installer-owned CI and host identifiers: GITHUB_REPOSITORY, GITHUB_SHA, GITHUB_REF, GITHUB_WORKFLOW, RUNNER_NAME, os.hostname(), and npm user-agent. When a build system misresolves the internal name to the public registry, this postinstall runs automatically and discloses internal repository, workflow, commit, and runner identifiers to a third-party endpoint. The package self-identifies as a Bugcrowd research canary, but self-labeling does not change the mechanism: installer-owned metadata leaves the machine at install time to a non-first-party destination via a namespace-squat.

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

3 flagged

9999.0.19999.0.29999.0.3

Indicators of compromise (SHA-256)

58ed68e675b2b6cde30e6b7c8e34077eda805a4bde64ca7cd2c68c6f4370ee5f

dd259558aaf77c18364c7c286e8e4d12cb6ea96c9b9b7bff8ef7bf1e05f750a4

9a690eb1bc2a09fccfb06b9531bbd7ec4da297737e700bd165096270b54c9995

d4759452d7dbcaf393bb33c7c6ec4018eafe54ba0388dbcf8cc1901be83de7cb

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

Campaign

IN-MAL-2026-008073IN-MAL-2026-008124GHSA-p92p-63h9-qrvcIN-MAL-2026-009808

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @luminarycloudinternal/frodo-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