T03 · Remote Payload Retrieval and Execution
- Location
guides/01-installation.md:17- Finding
Mutable Nightly Binaries Are Downloaded and Executed Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
guides/01-installation.md:17-23, 29-33, 41-45, 50-53;SKILL.md:74-75
Vulnerability Type: Remote payload retrieval and execution
Risk Level: MediumVulnerable Code
bash curl -L -o lightpanda \ https://github.com/lightpanda-io/browser/releases/download/nightly/lightpanda-x86_64-linux chmod a+x ./lightpanda ./lightpanda versionEquivalent installation instructions are provided for the other supported processor architectures and operating systems.
Technical Analysis
The instructions retrieve an executable from a mutable
nightlyrelease URL, grant it execute permission, and run it without checking a cryptographic signature or expected digest. Because the nightly artifact can change after the Skill has been reviewed, the executable that ultimately runs is not necessarily the artifact assessed during publication.HTTPS protects the transfer in transit but does not protect against compromise of the upstream repository, release workflow, maintainer account, or artifact storage. Merely running
lightpanda versionis not a safe validation step because a malicious executable can perform arbitrary actions before returning a plausible version string.Downloading a browser binary is necessary for the declared functionality. However, using a mutable release and omitting integrity verification exceeds the minimum supply-chain risk required to install that browser.
Attack Path
- An attacker compromises the upstream GitHub organization, maintainer account, release workflow, or nightly artifact.
- The attacker replaces one or more nightly binaries with a malicious executable.
- A user or AI agent follows the Skill's installation instructions.
curldownloads the attacker-controlled artifact.chmod a+xmakes the artifact executable../lightpanda versionor a later browser command executes the payload.- The payload performs action ...[truncated 677 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
nightlywith a reviewed, immutable release version. - Publish expected SHA-256 digests in the Skill or retrieve them from a separately authenticated release manifest.
- Verify the digest before granting execute permission or running the file.
- Prefer signed and notarized releases, and verify the publisher signature.
- Fail closed if any integrity or identity check fails.
- Avoid automatically executing downloaded artifacts; request informed user approval after displaying the source, version, and verified digest.
- Keep the installation in an unprivileged directory rather than moving the binary into a system-wide path until verification succeeds.
A hardened sequence should pin an immutable release, download both the binary and its authenticated checksum or signature, verify it, and only then make the file executable.
- Replace
