Quantum Systems, the German drone maker, says it found "an active cyberattack by hostile actors" at the end of October and contained it. Der Spiegel and the Financial Times, citing internal sources, report that the attackers placed a malicious file on the server that sends updates for the company's QBase mission-planning software. The company says its drones are safe to operate. If that account holds up, the lesson reaches well beyond defense: any manufacturer, engineering firm or production shop that ships software, firmware or configuration files to customers runs an update channel that attackers would like to borrow.
What Quantum Systems and the reporting say
In a statement dated November 12, 2026, Quantum Systems says it "identified a cybersecurity incident at the end of October 2026," that an internal investigation "revealed an active cyberattack by hostile actors," and that "the threat was contained thanks to the swift response of our IT and security teams in close and transparent collaboration with the authorities." It says there is "no risk in operating Quantum Systems' unmanned systems for the end users and the operators," that it reported the incident to the relevant authorities, and that the investigation continues with state authorities and outside experts.
BleepingComputer, summarizing Der Spiegel and the Financial Times, reports that the compromise came through a malicious QBase update file delivered from the vendor's update distribution server, and that it is unclear how many customers installed it. According to Reuters, a company spokesperson said the Bundeswehr was the only customer to ground its systems, as a precaution, and that "the fleet is operating normally around the globe."
What we are not claiming: The update-server detail comes from press reports citing unnamed sources; Quantum Systems' own statement does not describe how the attack worked. The company has not named the attackers, and we are not attributing it to anyone. We are not saying any drone was taken over, any customer system was damaged, any data was stolen, or that ransomware was involved. We do not know how many customers received or installed the reported update.
Why this matters to manufacturers, engineering firms and production shops
Plenty of small and mid-sized industrial firms now ship code along with hardware: controller firmware, configuration utilities, PLC programs, show-control files for exhibit builds, or a desktop app that talks to the machine. Customers trust whatever arrives through that channel because it comes from you. An attacker who gets onto your build machine, your download server or the account that publishes updates can turn that trust against your customers, and your name ends up on the incident report.
The same risk runs in the other direction. Your own shop floor installs vendor updates for CNC software, CAD and CAM tools, building controls and remote-support agents, often automatically and with administrator rights.
What to do this week
- List every update channel you control. Write down where customer-facing software and firmware are built, where they are hosted (website, file share, cloud bucket, vendor portal), and which accounts can publish them.
- Lock down the publishing accounts. Require phishing-resistant MFA on the accounts and servers that build or upload releases, remove former staff and contractors, and keep build machines off general email and web browsing.
- Sign what you ship and tell customers how to check it. Code-sign installers and firmware, publish checksums through a separate channel, and keep signing keys off everyday workstations, ideally in a hardware token or managed key service.
- Watch for releases nobody scheduled. Set an alert for any new file or version appearing on your download or update server, and make sure a person reviews it. Spiegel reports that an unscheduled update is what raised the alarm here.
- Stage vendor updates on your own floor. For machine-control and engineering software, test updates on one workstation before rolling them out, and don't let production PCs auto-install from the internet without review.
- Agree on a customer-notice plan. Decide in advance who tells customers to pause updates or ground equipment, and how you'll reach them quickly if your update channel is ever in doubt.
The takeaway for IT decision-makers
If you ship software or firmware, your update channel is part of your product, and it needs the same protection as your bank account. Know who can publish, sign what you ship, alert on surprise releases and have a plan to warn customers. On the receiving side, treat vendor updates to production machines as changes you test and approve, not something that installs itself.
Sources
- Quantum Systems: Statement on Cyber Incident (Nov 12, 2026)
- BleepingComputer: German military drone operations disrupted by cyberattack (Nov 13, 2026; citing Der Spiegel and the Financial Times)
- Reuters via CNA: Quantum Systems says grounded German military drones flying again after cyberattack (Nov 13, 2026)
- DroneNews.org: Bundeswehr grounds Quantum Systems' Vector drones for a time after a cyberattack (Nov 12, 2026)