Proprietary 2019-04-30 · 14 days ·Backdoor, Remote Access, Data Exfiltration

ASUS WebStorage update served PLEAD

BlackTech abused ASUS WebStorage's HTTP update flow to deliver PLEAD in Taiwan. The legitimate signed client executed a malicious update pushed through likely router-level interception.

Story

ASUS WebStorage was not the same incident as ShadowHammer. In late April 2019, ESET saw the legitimate AsusWSPanel.exe process create and execute PLEAD malware on systems in Taiwan. The process belonged to ASUS WebStorage and was digitally signed by ASUS Cloud Corporation.

ESET's favored explanation was router-level man-in-the-middle delivery. ASUS WebStorage requested and transferred updates over HTTP, then executed the downloaded file without validating its authenticity. If an attacker controlled the network path, the update mechanism became a delivery slot.

The surrounding tradecraft pointed to BlackTech. ESET noted that PLEAD had been used by the group in regional espionage, and that affected organizations often had internet-accessible routers from the same manufacturer. Prior BlackTech operations had also used compromised routers as command infrastructure.

The payload was PLEAD, a backdoor built for espionage. Reporting described host and file collection, command execution, file upload, and a document-exfiltration module that used Google Drive. ASUS WebStorage supplied the trust boundary; the router supplied the position.

Affected Artifacts

ASUS WebStorage

windows update · asuswebstorage.com · Update
Observed
2019-04-30 to 2019-05-14
Compromised Versions
Unknown
Fixed
Not listed
Evidence
distribution: asuswebstorage.com, file: AsusWSPanel.exe, malware: PLEAD, actor: BlackTech , +7 more
  • ESET assessed router-level man-in-the-middle delivery as the most probable scenario and said a supply-chain compromise could not be fully discounted.
  • Start date is approximate; ESET described the activity as late April 2019.
  • Exact affected ASUS WebStorage versions and hashes were not published in the cited sources.

Incident Context

Motive
Espionage
Attribution
Group
Cause
Insecure Update Mechanism
Transitive
No
Actor
BlackTech

External References

Source record: proprietary/asus-webstorage/meta.yaml