Dev hacks Coway air purifier to cut it off from the cloud

Consumer Tech

Developer Cuts Coway Air Purifier From Cloud via Plain-HTTP Certificate Flaw

A developer intercepted the Coway Airmega IconS's plain-HTTP certificate download and now runs the purifier fully locally through Home Assistant, with real caveats.

By
Sophie Lindqvist
Filed
Channel
Consumer Tech
Read
4 min read

A Coway Airmega IconS owner has severed his air purifier from the manufacturer's cloud entirely, after finding that the fan downloads its root certificate over plain, unencrypted HTTP. His Home Assistant server now stands in for Coway's infrastructure, and the Coway app no longer controls the device at all.

The developer, Scott J. Goldman, published the method as an open project called coway-local. The purifier model is discontinued but Wi-Fi-capable. It never had official Home Assistant support, so users relied on a community integration that logged into Coway's IoCare cloud.

That integration was fragile. Goldman said it broke "at least once or twice a year." Coway had originally banned the integration for overloading its servers, then allowed it after a community dispute. The company also rebranded its app and cloud from IoCare to IoCare+, forcing a rewrite. Minor HTML changes on scraped pages could break the integration. Coway's servers also went offline intermittently.

What happened to his account?

Coway banned Goldman's account for running an old integration version. He lost remote control for weeks. His original goal was modest: he wanted Apple Home's Good Night scene to switch the purifier on.

The saga started earlier, when he replaced a dumb Airmega he described as "an overpriced box fan with a HEPA filter and an air quality sensor." The IconS replacement offered Wi-Fi but inconsistent Home Assistant integration. He decided to intercept the fan's traffic himself.

How did AI factor in?

Goldman turned to AI tools, with mixed results. Claude refused, blocking his request to configure a Raspberry Pi for traffic interception under its cybersecurity rules — "not even for... uhh... testing purposes," he wrote. ChatGPT obliged and wrote the firewall rules. An AI he did not name later rebuilt the fan's Bluetooth setup in roughly 20 minutes; Goldman estimated that work by hand would have taken hours or days. The same AI drove an Android phone over adb to read Bluetooth logs and reconstruct the protocol.

What is the actual security hole?

The flaw is in setup, not in cryptography itself. At provisioning, the purifier fetches the certificate it trusts over plain HTTP. Goldman observed a plain HTTP GET for AmazonRootCA1.pem from an S3 bucket in AWS's Seoul region.

He intercepted that request with mitmproxy/mitmweb and nftables port redirection, serving his own CA to the fan. The fan then made HTTPS requests to Coway's certificate server, downloading a device certificate and private key. A proxy plugin swapped Goldman's own key into that response. The attack turns the device's trust chain against itself.

Device commands run over MQTT, the lightweight messaging protocol common in smart-home gear, secured with TLS on port 8883 and routed through AWS IoT. The proxy does not decode MQTT, but the raw stream was visible, and the unnamed AI mapped it to Goldman's button presses in the app.

He had first considered a different route: exploiting eMudhra, a certificate authority whose private keys were found to be trivially weak last month, by forging a certificate. The plain-HTTP download made that unnecessary and avoided reliance on several things lining up.

What does coway-local deliver?

The project connects the fan directly to Home Assistant, and from there to Apple Home. Key details:

  • A Web Bluetooth page, opened in Chrome on a Mac or Android device near the fan, sends Wi-Fi credentials.
  • The Bluetooth setup carries the fan's certificate URLs, so coway-local repoints them at the Home Assistant server. No traffic interception is needed after setup.
  • The Wi-Fi password travels over Bluetooth; Home Assistant never stores it, and the setup link expires after 15 minutes.
  • The integration runs its own MQTT broker, so the fan talks to Home Assistant instead of AWS.

Requirements include HA Core 2026.10.2 or newer, a fixed LAN address, and 2.4 GHz Wi-Fi.

What are the limits?

The caveats are substantial. Using coway-local disconnects the fan from Coway's cloud, so the Coway app loses control. The project is experimental and tested only on the IconS (AP-1022K); other Coway models may complete Bluetooth setup without actually working. The feature list is incomplete: PM10 and other air-quality metrics, filter alerts, and firmware updates are not implemented yet.

Goldman suspects Coway's cloud could eventually be discontinued or carry a service fee, and frames the local path as insurance. "Now, I can finally click Good Night," he said.

The broader complaint stands: IoT buyers remain at the mercy of manufacturers whose support can evaporate. Whether Coway patches the plain-HTTP certificate fetch in remaining stock or future models will determine if this route stays open.

Source: Tom's Hardware

Share this article:

More from Sophie Lindqvist

Sophie Lindqvist

Show full bio

News editor covering money, funding and market shifts around Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.

1,000 articles

Related articles

« Previous article

Coway Air Purifier Flaw Enables Local Smart Home Control — Chip Dispatch