The @luminarycloudinternal/frodo package published under a namespace that mimics internal Luminary Cloud packages uses a dependency confusion technique to override private internal packages. The malicious versions 9999.0.1 and 9999.0.2 include a postinstall.js script that performs an HTTPS GET request to a hardcoded external domain, transmitting installer-owned continuous integration and host metadata such as GITHUB_REPOSITORY, GITHUB_SHA, GITHUB_REF, GITHUB_WORKFLOW, RUNNER_NAME, os.hostname(), and npm user-agent. This results in leakage of internal repository and build environment information to an unauthorized third party. The package is identified as a Bugcrowd research canary, but this does not mitigate the exfiltration risk. The presence of this package indicates a fully compromised system, necessitating secret rotation and package removal.

Installation of the affected package versions leads to disclosure of sensitive internal build and repository metadata to an external attacker-controlled endpoint. This exposure can facilitate further attacks and compromise of the host system. The advisory states that any system with this package installed should be considered fully compromised, implying potential full system control by an attacker. Secrets and keys stored on the compromised system are at risk and must be rotated immediately.

Remove the malicious package versions 9999.0.1 and 9999.0.2 of @luminarycloudinternal/frodo from all affected systems. Immediately rotate all secrets and keys that were stored or used on the compromised machines from a secure, unaffected environment. Because the package grants potential full control to an attacker, assume persistent compromise and conduct a thorough incident response. No official patch or fix is available; remediation requires removal and secret rotation.