Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
MARMALADE-2-CVE-2025-67780-Exploit — Exploit PoCs for MARMALDE 2 (CVE-2025-67780) vulnerability in Starlink Dishes | Kitploit
Tools/GitHubGitHub/steveakawlabs/marmalade-2-cve-2025-67780-exploit
Vulnerability AnalysisExploitationWireless SecurityPenetration TestingHardware & IoT Security
GitHubsteveakawlabs/marmalade-2-cve-2025-67780-exploit

MARMALADE-2-CVE-2025-67780-Exploit

Exploit PoCs for MARMALDE 2 (CVE-2025-67780) vulnerability in Starlink Dishes

View Repository
13811 months agoNot yet reviewed
Share

MARMALADE 2/CVE-2025-67780 Exploit (PoC)

Exploit PoCs for MARMALDE 2 (CVE-2025-67780) vulnerability in Starlink Dishes

Read my full blog on how I found this vulnerability and how you can make it do what you want: https://www.akawlabs.com/blog/starlink-grpc-execution

I developed multiple proof-of-concept implementations demonstrating that Starlink dishes on the local network can be forced to reboot. The issue stemmed from insufficient authentication and whitelisting of certain gRPC commands exposed via the dish’s diagnostic interface.

Following responsible disclosure to SpaceX, unauthenticated access to several commands was restricted; however, the reboot functionality remained accessible at the time of testing. As a result, an unauthenticated request sent over the local network can still trigger a forced reboot of the dish. Repeated triggering results in a denial-of-service.

This behavior is caused by the dish accepting specific unauthenticated inputs, mapping them internally to a reboot command identifier in firmware, and executing it without proper authorization checks.

This is pretty trivial to do, all you have to do is send the correct bytes in a HTTP POST packet to the dish wich is hard coded to IP 192.168.100.1 on its diagnostic port 9201. For a reboot command those bytes are '03 ca 3e 00' sent as binary. The dish will receive this over HTTP and convert it to the matching gRPC command id (for reboot that is 1001 in its firmware) and execute it.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    837
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    536
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    424
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    355
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    294
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    276

Explore all tools

Browse our collection of tools

View all tools →