2022 · S - Other service activities · State-sponsored espionage intrusion via exploited internet-facing remote-access appliance
Analysed 2026-11-07 by Hermes
Open this case in the tool →State-sponsored espionage intrusion via exploited internet-facing remote-access appliance
Expertise to Execution
Evidence coverage: 2/6 stages, weight 15/60
Decisive stage: entry (clearest evidence) · Alternative: none defensible
(1) The expectation at the victim was a routine one for any organisation exposing a corporate remote-access login portal: internet-facing identity infrastructure is patched against published vulnerabilities and is logged well enough to see and scope what happens on it - the ACSC advisory itself frames exactly these as the required mitigations, including applying patches or mitigations to internet-facing infrastructure quickly (within 48 hours per the coverage of the advisory). (2) In practice, from April 2022 APT40 exploited publicly known RCE, privilege-escalation and authentication-bypass vulnerabilities in the remote-access identity appliance behind that portal, placed web shells on all three load-balanced hosts, harvested several hundred genuine username/password pairs in clear text plus MFA codes and JWTs, and scraped an internal SQL server; the organisation's own monitoring noticed nothing - ACSC's notification in May 2022 preceded the organisation's discovery of the April-created web shell, and because the appliance did not log the attacker's commands the full extent of the activity could never be determined. (3) This is a knowing-doing gap inside the material column, not a strategy gap: the remedy (patching a widely publicised CVE in a mainstream remote-access product, logging an internet-facing appliance) sat with the organisation's own technical specialists and simply was not executed on the exposed portal, and nothing in the sources shows leadership deciding, deferring, under-resourcing or accepting the gap - for this anonymised victim no doctrinal artefact or leadership decision is documented at all. The classification rests on the entry stage (clearest evidence: the advisory states the server was vulnerable to these CVEs at the time); the detection gap points to the same type. The exact exploitation method is stated as likely rather than proven and multiple actors may have been involved, which is why the mechanism is only partly incident-confirmed; the victim's remediation and cooperation mean no recovery or response gap is claimed. RM18 (Expertise to Execution lens): the exploited vulnerabilities in the remote-access identity product were published and remediable at the time of the intrusion, yet the internet-facing portal stayed unpatched, so the delay in executing a known fix handed APT40 its foothold (causal role: Enabling). RM34 (Expertise to Execution lens): the organisation's own monitoring and alert handling did not surface about a month of web-shell activity and credential capture on its crown-jewel remote-access server; detection came from an external agency notification rather than from its defences (causal role: Obscuring). RM33 (Expertise to Execution lens): the appliance generated no usable command logs, so when ACSC investigated, experts could not reconstruct the full extent of the activity or determine what data was taken (causal role: Obscuring).
RM18 — Vulnerability / patch latencyRM34 — Monitoring / detection / alert-handling gapRM33 — Logging / forensic-readiness gapVictim is anonymised in the primary source (ASD/ACSC advisory case study 2, which matches this row: April 2022 compromise, May 2022 ACSC notification, remote-access portal appliance), so Country is left blank - not disclosed anywhere in the advisory or coverage (see the Sector note below). Impact mismatch with the row: the row says hijacking without misuse, no disruption and no data breach/exfiltration, but the primary advisory documents exfiltration of several hundred genuine username/password pairs, MFA token values and JWTs and the scraping of an internal SQL server; classified on the primary advisory. Wording nuance: the row says ACSC notified the organisation of malicious software on the server, while the advisory says ACSC notified of suspected malicious activity and the organisation then discovered the malicious software (web shell dated April) itself. The advisory's case study 1 (July-September 2022) is a different, also-anonymised organisation and was not used. No related_rows in the case file. The initial exploitation method is stated as likely, not proven, and multiple actors may have been involved; the advisory was read from the downloaded PDF (direct fetch to cyber.gov.au was retried via requests after a curl stream error). Sector: the victim's branch of activity is nowhere disclosed (the advisory shows only corporate-network features - AD domain, VDI, hosting-provider environment - pointing to a private-sector company of unknown industry), but the output check requires exactly one CBS SBI entry, so the residual section S Other service activities is recorded as a placeholder pending researcher review; the method spec would leave Sector blank here. Link check: cyber.gov.au was unreachable at check time (timeout); the page was opened and read during research (the advisory PDF was downloaded in full and read with pdftotext). Unattended run: nothing required consent.