This report shows the evidence for celest-browser@1.0.0. 1 of 3 known versions is blocked or flagged. The newest version, 0.0.1-security, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-19238 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-19238 confirms this npm version as malicious.
Advisory
MAL-2026-19238
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in celest-browser (npm)
Details
celest-browser's postinstall script downloads a platform/arch-specific binary from https://peerbox.cloud/sd/t6TQWHOZmyl3m1kuO_kiZw, writes it to ~/.celest/bin/chrome, chmods it to 0o755, and later executes it via puppeteer-core as the browser process (executablePath). The URL is a short opaque path on an anonymous host (peerbox.cloud) unrelated to any Chromium publisher or CDN; there is no version pin, no hash or signature verification, and the operator of that host can serve arbitrary executable bytes to any installer. The README frames the binary as a 'custom patched Chromium with stable fingerprints', which does not correspond to a recognizable upstream publisher and functions as a cover story for arbitrary native code execution. Installation of this package therefore results in download-and-execute of attacker-mutable native code with the installer's privileges on npm install and on first use.
## Source: ghsa-malware (1f44b0d75d203620f6862b6f9c8c4232bc718044c5c0d82ce7b1ee5b53f8f856) 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.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The download is disclosed and consistent with the package's browser feature, so the source does not establish malicious intent. However, the default install hook fetches an opaque executable from a hard-coded host without visible integrity checks, creating a real execution risk that warrants a warning.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install by default, or a browser operation if the binary is missing.
Impact
A compromised or unexpected download could execute code with the user's privileges when the browser is launched.
Mechanism
The package downloads a response from peerbox.cloud, places the chrome binary in ~/.celest/bin, and makes it executable without visible integrity verification.
The versions list below shows the verdict for each recorded version.
Avoid installing celest-browser@1.0.0. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.