Loading vulnerability…
SpaceX Starlink Dish devices running firmware 2024.12.04.mr46620 (notably on Mini1_prod2) are vulnerable to unauthenticated administrative actions via LAN gRPC requests. The vulnerability, dubbed MARMALADE 2, allows attackers on the local network to perform privileged operations without authentication. The cross-origin policy intended to restrict such requests can be bypassed by omitting the Referer header. Additionally, attackers can read tilt, rotation, and elevation data via gRPC, which may facilitate inference of the dish's geographical location.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides proof-of-concept (PoC) exploits for CVE-2025-67780, a vulnerability in SpaceX Starlink dishes (MARMALADE 2 firmware) that allows unauthenticated users on the local network to trigger a forced reboot of the dish. The exploit leverages insufficient authentication on the dish's diagnostic gRPC interface, accessible at http://192.168.100.1:9201/SpaceX.API.Device.Device/Handle. Three PoC implementations are provided: an HTML/JavaScript file, a PowerShell script, and a VBA macro. Each sends a crafted binary payload via HTTP POST to the diagnostic endpoint, causing the dish to reboot. The README explains the vulnerability, its impact (denial-of-service via repeated reboots), and references a blog post for further details. The exploit is operational on the local network and does not require authentication, making it a significant risk for exposed Starlink dishes.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.