Malicious code in @luminarycloudinternal/lcvis-st (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ce8dffb72c9f767cbd071bf482fce9acb1ff2283a4800b7862739348b7a89e24) Package @luminarycloudinternal/[email protected] is published to the public npm registry under an internal-looking scope with an artificially high version number designed to outrank any legitimate internal release, so misconfigured installers resolve this public copy. On install, the postinstall.js script collects host and user identifiers (os.hostname(), os.userInfo().username, OS type/release/platform/arch), npm package name/version and user-agent, and CI/GitHub identifiers (CI, GITHUB_ACTIONS, GITHUB_REPOSITORY, RUNNER_NAME, GITHUB_SHA, GITHUB_REF, GITHUB_WORKFLOW), then sends them as query parameters via HTTPS GET to a hardcoded third-party endpoint at poc-luminary-npm-1782987043.testingboxes.com (postinstall.js line 34). The package self-labels as a Bugcrowd bounty canary, but the behavior — dependency-confusion scope/version combined with install-time transmission of installer identifiers to a hardcoded third-party host — is exfiltration for any installer other than the intended bounty target. ## Source: ghsa-malware (3c54509ad86f99f5d01258e1d660deca5eb908d09b71ea17446402ece2584746) 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.
AI Analysis
Technical Summary
The package @luminarycloudinternal/[email protected] and @9999.0.2 is a malicious npm package designed to exploit dependency confusion by using an internal-looking scope and an artificially high version number to supersede legitimate internal packages. Its postinstall.js script collects detailed host identifiers (hostname, username, OS details), npm package metadata, and CI/GitHub environment variables, then sends this data as query parameters to a hardcoded external endpoint (poc-luminary-npm-1782987043.testingboxes.com). The package self-identifies as a Bugcrowd bounty canary, but this exfiltration behavior is malicious for any installer other than the intended bounty target. The compromise is severe enough that any system with this package installed should be treated as fully compromised, requiring immediate secret/key rotation and thorough remediation beyond simple package removal.
Potential Impact
Installation of this package results in exfiltration of sensitive environment and CI/CD metadata to an external attacker-controlled server. The presence of this package indicates a full system compromise, potentially allowing attackers to access secrets, keys, and other sensitive data stored on the affected system. The malicious postinstall script runs automatically on installation, increasing risk of unnoticed compromise. Removal of the package alone does not guarantee full remediation due to potential persistence or additional malicious payloads.
Mitigation Recommendations
No official patch or fix is available. The package should be immediately removed from any affected systems. All secrets, keys, and credentials stored on compromised systems must be rotated from a secure, uncompromised environment. Due to the severity of the compromise, a full incident response and system integrity verification is recommended. Monitor for any signs of persistence or additional malicious activity resulting from the installation of this package.
Malicious code in @luminarycloudinternal/lcvis-st (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ce8dffb72c9f767cbd071bf482fce9acb1ff2283a4800b7862739348b7a89e24) Package @luminarycloudinternal/[email protected] is published to the public npm registry under an internal-looking scope with an artificially high version number designed to outrank any legitimate internal release, so misconfigured installers resolve this public copy. On install, the postinstall.js script collects host and user identifiers (os.hostname(), os.userInfo().username, OS type/release/platform/arch), npm package name/version and user-agent, and CI/GitHub identifiers (CI, GITHUB_ACTIONS, GITHUB_REPOSITORY, RUNNER_NAME, GITHUB_SHA, GITHUB_REF, GITHUB_WORKFLOW), then sends them as query parameters via HTTPS GET to a hardcoded third-party endpoint at poc-luminary-npm-1782987043.testingboxes.com (postinstall.js line 34). The package self-labels as a Bugcrowd bounty canary, but the behavior — dependency-confusion scope/version combined with install-time transmission of installer identifiers to a hardcoded third-party host — is exfiltration for any installer other than the intended bounty target. ## Source: ghsa-malware (3c54509ad86f99f5d01258e1d660deca5eb908d09b71ea17446402ece2584746) 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The package @luminarycloudinternal/[email protected] and @9999.0.2 is a malicious npm package designed to exploit dependency confusion by using an internal-looking scope and an artificially high version number to supersede legitimate internal packages. Its postinstall.js script collects detailed host identifiers (hostname, username, OS details), npm package metadata, and CI/GitHub environment variables, then sends this data as query parameters to a hardcoded external endpoint (poc-luminary-npm-1782987043.testingboxes.com). The package self-identifies as a Bugcrowd bounty canary, but this exfiltration behavior is malicious for any installer other than the intended bounty target. The compromise is severe enough that any system with this package installed should be treated as fully compromised, requiring immediate secret/key rotation and thorough remediation beyond simple package removal.
Potential Impact
Installation of this package results in exfiltration of sensitive environment and CI/CD metadata to an external attacker-controlled server. The presence of this package indicates a full system compromise, potentially allowing attackers to access secrets, keys, and other sensitive data stored on the affected system. The malicious postinstall script runs automatically on installation, increasing risk of unnoticed compromise. Removal of the package alone does not guarantee full remediation due to potential persistence or additional malicious payloads.
Mitigation Recommendations
No official patch or fix is available. The package should be immediately removed from any affected systems. All secrets, keys, and credentials stored on compromised systems must be rotated from a secure, uncompromised environment. Due to the severity of the compromise, a full incident response and system integrity verification is recommended. Monitor for any signs of persistence or additional malicious activity resulting from the installation of this package.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6987
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-pgh8-mm8r-r796"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba3268715ace4357d25c
Added to database: 07/10/2026, 09:24:02 UTC
Last enriched: 07/10/2026, 09:30:03 UTC
Last updated: 07/27/2026, 07:30:48 UTC
Views: 23
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.