Skip to navigation

Threat reportSupply ChainTL-2026-1749

CubePilot Drone Autopilot Vendor Hit by DNS Hijacking, Enabling Traffic Interception and Fraudulent TLS Certificates

highACTIVE

On July 24, 2026, an unattributed attacker seized DNS control of cubepilot.org, obtained fraudulent TLS certificates covering all subdomains, and intercepted traffic to the OEM portal, community forum, documentation site, and ERP portal of CubePilot — a Blue UAS-listed Australian drone autopilot vendor.

Key facts

IdentifiersTL-2026-1749
SeverityHIGH
Affected productsCubePilot Global Pty Ltd cubepilot.org web infrastructure (OEM portal, community forum, documentation site, ERP portal) and firmware distribution for the Cube autopilot family (Cube Orange, Cube Orange+, Cube Blue, Cube Blue H7) and Here3/Here4 GNSS modules
ToolsBlue UAS (DoD cleared UAS list)
MITRE ATT&CK techniquesT1036 Masquerading, T1056 Input Capture, T1195 Supply Chain Compromise, T1199 Trusted Relationship, T1491 Defacement, T1553 Subvert Trust Controls, T1557 Adversary-in-the-Middle, T1565 Data Manipulation, T1583 Acquire Infrastructure, T1584 Compromise Infrastructure, T1588 Obtain Capabilities, T1590 Gather Victim Network Information and 3 more in the attack flow
MotivationUNKNOWN
Target sectorsdefense, government administration, agriculture, critical-infrastructure, technology-manufacturing
Target regionsaustralia, North America, Global
Detection rules9 (1 shown free)
Sources8 cited sources

Detection coverage

As of 2026-07-28, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1749 across Splunk SPL, Microsoft KQL and Sigma, covering 16 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Self-Signed / Attacker-Issued Certificate Installed to User Trust Store (Windows)

Detects PowerShell generating a self-signed certificate and importing it into the CurrentUser\Root trust store — the local-trust-subversion pattern reproduced in the DETECT-phase simulation as a stand-in for the fraudulently issued, domain-validated certificate CubePilot's attacker obtained via hijacked DNS. A cert trusted this way lets an AiTM proxy present browser-trusted HTTPS for the spoofed domain.

  • Languages: Splunk SPL, Microsoft KQL, Sigma
  • ATT&CK: T1553.004, T1588.004
  • Data sources: sysmon, windows_security, powershell_operational
  • Severity: critical
  • Confidence: high

Splunk SPL

index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" earliest=-24h EventCode=1
    (CommandLine="*New-SelfSignedCertificate*" OR (CommandLine="*Import-Certificate*" AND CommandLine="*Cert:\\CurrentUser\\Root*"))
| table _time host User Image CommandLine
| sort - _time

Microsoft KQL

DeviceProcessEvents
| where Timestamp > ago(24h)
| where FileName in~ ("powershell.exe","pwsh.exe")
| where ProcessCommandLine has "New-SelfSignedCertificate"
    or (ProcessCommandLine has "Import-Certificate" and ProcessCommandLine has @"Cert:\CurrentUser\Root")
| project Timestamp, DeviceName, AccountName, ProcessCommandLine
| sort by Timestamp desc

Sigma

title: Self-Signed Certificate Created and Imported to CurrentUser Root Store
id: 2e4f6a80-1c3d-4b5e-9f7a-8b9c0d1e2f3a
status: experimental
description: Detects PowerShell creating a self-signed certificate and importing it into the CurrentUser\Root trust store, the local trust-subversion pattern used to stand in for a fraudulently issued domain-validated certificate in the CubePilot (TL-2026-1749) DNS-hijack detection-validation simulation.
references:
    - https://www.bleepingcomputer.com/news/security/cubepilot-drone-software-dev-hit-by-dns-hijacking-to-intercept-traffic/
author: Threadlinqs Team
date: 2026-07-29
tags:
    - attack.defense-evasion
    - attack.t1553.004
    - attack.t1588.004
logsource:
    category: process_creation
    product: windows
detection:
    selection_create:
        CommandLine|contains: 'New-SelfSignedCertificate'
    selection_import:
        CommandLine|contains|all:
            - 'Import-Certificate'
            - 'Cert:\CurrentUser\Root'
    condition: selection_create or selection_import
falsepositives:
    - Approved internal PKI or dev-certificate provisioning tooling
level: high

Known false positives:

  • Legitimate internal PKI/dev-cert tooling that provisions self-signed certs to CurrentUser\Root for approved internal testing
  • Software deployment tooling that installs code-signing or internal CA roots via similar cmdlets

Tuning notes: Allowlist known internal PKI automation accounts/hosts; alert with higher confidence when the certificate's Subject/SAN matches a monitored external vendor domain rather than an internal name.

8 more detection rules (Splunk SPL, Microsoft KQL, Sigma) · unlock with TL Creds. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • Anomalous DNS Resolution for Registered Vendor Domain (Cloud DNS Telemetry) · unlock with TL Creds
  • Unexpected Certificate Transparency Log Issuance for Monitored Vendor Domain · unlock with TL Creds
  • Anomalous Vendor-Domain DNS Resolution Correlated with Payment-Fraud Lure Email · unlock with TL Creds
  • Unauthorized /etc/hosts Modification Followed by Local HTTP Listener — Linux AiTM Staging · unlock with TL Creds
  • Firmware Integrity Verification Failure — Supply-Chain Tamper Quarantine · unlock with TL Creds
  • Loopback HTTP Listener or Command-Line Credential Submission — AiTM Capture Artifact · unlock with TL Creds
  • Unauthorized Hosts File Modification — DNS Hijack Precursor (Windows Endpoint) · unlock with TL Creds
  • AiTM Credential Capture on Hijacked Vendor Portal Login Endpoint · unlock with TL Creds

Indicators of compromise

As of 2026-07-28, Threadlinqs Intelligence tracks 16 indicators of compromise for TL-2026-1749.

Sample indicators (1 of 16)

  • Domain: cubepilot[.]org

Defanged, TLP:CLEAR. Full set of 16 indicators: unlock with TL Creds.

16 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

CubePilot regained control the same day, revoked the certificates, and flagged firmware downloaded during the July 24-25 window as potentially unsafe pending integrity checks.

CubePilot Global Pty Ltd, a Geelong, Australia-based manufacturer of drone flight-controller hardware (the Cube autopilot family) whose products sit on the US Department of Defense's Blue UAS cleared list through 2027, disclosed that an attacker gained control of the DNS settings for its primary domain, cubepilot.org, on July 24, 2026. Because DNS control determines which certificate authority domain-validation challenges resolve against, the attacker was able to obtain valid, fraudulently-issued TLS certificates covering every cubepilot.org subdomain. This let the attacker present browser-trusted HTTPS connections while redirecting visitors of CubePilot's OEM portal, community/support forum, documentation site, and ERP portal to attacker-controlled infrastructure — a domain-hijack-enabled adversary-in-the-middle position rather than a vulnerability in any CubePilot product.

CubePilot states that any credentials entered on its services on July 24, including the OEM portal and forum, may have been captured, and has urged affected users to rotate reused passwords. Because the compromise briefly sat astride CubePilot's software/firmware distribution channel, the company additionally flagged firmware images downloaded between July 24 and July 25, 2026 as not yet confirmed safe, while firmware obtained before July 24 is considered unaffected. CubePilot also warned customers that any payment request purporting to come from the company should be verified by phone before acting on it, anticipating possible follow-on business-email-compromise-style fraud using data or trust harvested during the compromise window.

CubePilot's response, per its public statement and CEO Philip Rowse, included regaining domain control same-day, revoking the fraudulent certificates, preserving evidence, notifying affected providers, taking the OEM portal, forum, documentation site, and ERP portal offline as a precaution, and reporting the incident to the Australian Cyber Security Centre (ACSC) and law enforcement. As of disclosure, no CVE, malware sample, attacker infrastructure (IPs/domains), or attribution had been published; the incident is a vendor-infrastructure/DNS-and-PKI-trust compromise rather than a code-level vulnerability, but it is supply-chain relevant because CubePilot's Cube autopilot hardware and ArduPilot/PX4-compatible firmware are widely used across defense, government, agriculture, surveying, and search-and-rescue drone deployments, including under the AUKUS-aligned Blue UAS program.

MITRE ATT&CK techniques by tactic:

Defense Evasion

T1036 Masquerading

Credential Access

T1056 Input Capture

Initial Access

T1195 Supply Chain Compromise; T1199 Trusted Relationship

Impact

T1491 Defacement; T1565 Data Manipulation; T1657 Financial Theft

defense-impairment

T1553 Subvert Trust Controls

Collection

T1557 Adversary-in-the-Middle

Resource Development

T1583 Acquire Infrastructure; T1584 Compromise Infrastructure; T1588 Obtain Capabilities; T1608 Stage Capabilities

Reconnaissance

T1590 Gather Victim Network Information

stealth

T1684.001 Impersonation

Remediation

Patches

  • CubePilot regained DNS control and revoked the fraudulently issued TLS certificates on 2026-07-24 (vendor-side remediation, already applied)

Immediate actions

  • Do not flash firmware images downloaded between 2026-07-24 and 2026-07-25 until CubePilot confirms their integrity
  • Rotate any password that was entered on cubepilot.org, the OEM portal, or the community forum on 2026-07-24, especially if reused on other services
  • Verify any payment request purporting to be from CubePilot by phone through a known, previously-established contact before acting on it
  • Treat credentials, session tokens, or sensitive data submitted to any cubepilot.org subdomain on 2026-07-24 as potentially exposed

Workarounds

  • Continue using previously downloaded (pre-2026-07-24) firmware images, which the vendor considers safe, pending integrity confirmation of the July 24-25 batch
  • Avoid logging into cubepilot.org-hosted services until the vendor confirms full restoration and integrity of the affected portals

Longer-term hardening

  • Enable registrar-level MFA, registry lock, and change-notification alerting on business-critical domains to prevent unauthorized DNS modification
  • Monitor Certificate Transparency logs for unauthorized certificate issuance against owned domains
  • Adopt DNSSEC and restrictive CAA records limiting which certificate authorities may issue for the domain
  • Maintain an out-of-band, non-DNS-dependent incident-communication channel for supply-chain customers during future domain-level incidents

Affected and fixed versions

  • CubePilot Global Pty Ltd — cubepilot.org web infrastructure (OEM portal, community forum, documentation site, ERP portal) and firmware distribution for the Cube autopilot family (Cube Orange, Cube Orange+, Cube Blue, Cube Blue H7) and Here3/Here4 GNSS modules
    Vulnerable versions: Firmware images downloaded 2026-07-24 through 2026-07-25 (integrity not yet confirmed by vendor at time of disclosure)
    Fixed in: Firmware images downloaded prior to 2026-07-24 (confirmed safe by vendor)

Timeline

  • CubePilot preserves evidence, notifies affected providers, and reports the incident to the Australian Cyber Security Centre (ACSC) and law enforcement.
  • CubePilot takes the OEM portal, community forum, documentation site, and ERP portal offline as a precaution while it investigates; CEO Philip Rowse confirms the ERP portal shutdown.
  • The fraudulently issued TLS certificates covering locked-ioc-3 subdomains are revoked.
  • CubePilot regains control of the locked-ioc-3 domain the same day the hijack is detected.
  • CubePilot warns that credentials entered on any of its services on July 24, including the OEM portal and forum, may have been captured by the attacker.
  • Using the hijacked DNS control, the attacker obtains fraudulently issued TLS certificates covering all locked-ioc-3 subdomains, enabling browser-trusted HTTPS traffic interception.
  • Attacker gains control of the DNS settings for locked-ioc-3, the primary domain for CubePilot's OEM portal, community forum, documentation site, and ERP portal.
  • CubePilot flags firmware images downloaded between July 24 and July 25 as not yet confirmed safe pending integrity checks, while firmware obtained before July 24 is deemed unaffected.
  • BleepingComputer and other outlets publicly report the DNS hijacking incident and CubePilot's response.

Sources cited

Previous and next in supply chain

Further reading

Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats