Certain Kia Motors Head Unit software versions contain a command-injection vulnerability involving the micomd daemon. An attacker able to execute this daemon may inject unauthorized commands, trigger unintended head-unit functionality, and generate CAN frames for transmission on the vehicle Multimedia CAN (M-CAN) bus.
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 contains a single Metasploit post-exploitation module targeting Kia Motors head units running Android, specifically exploiting CVE-2020-8539. The module, named 'KOFFEE', allows an attacker with an active Meterpreter session on a vulnerable head unit to execute arbitrary commands via the 'micomd' binary. The exploit provides a range of actions, including muting/unmuting the radio, adjusting volume and screen brightness, displaying navigation or warning messages, switching the head unit on/off, controlling the parking camera, changing instrument cluster settings, and injecting custom CAN bus frames. The module is highly operational, providing direct control over vehicle multimedia and CAN bus features. The only fingerprintable endpoint is the path to the 'micomd' binary ('/system/bin/micomd'). The exploit is not a detection script or a fake; it is a functional post-exploitation tool for vehicle head units. The code is written in Ruby and structured as a standard Metasploit post module.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.