Skip to content
skopnix
Detections
← All detectionsLinked actor

APT35

24 rules8 findings

The APT35 dossier →

  1. Behaviour (ATT&CK technique)

    LSASS memory dump via comsvcs.dll MiniDump (T1003.001)

    Requires both 'comsvcs' and the MiniDump export (by name or ordinal

    APT1 · APT15 · APT27 · APT28 · APT3 · APT32 · 35 more

    T1003.001conf 90SIGAQLXQL

  2. Behaviour (ATT&CK technique)

    certutil used to download a remote file (T1105)

    Needs certutil, a download switch and an http(s) URL together; certutil hashing, encoding or CA administration does not match.

    APT-C-36 · APT10 · APT15 · APT18 · APT23 · APT27 · 76 more

    T1105conf 80SIGAQLXQL

  3. Behaviour (ATT&CK technique)

    PowerShell download cradle executed from the command line (T1059.001)

    All three conditions must hold (PowerShell binary, a download method, an execute verb); plain Invoke-WebRequest file downloads and encoded management scripts do not match.

    APT-C-36 · APT10 · APT19 · APT27 · APT28 · APT29 · 71 more

    T1059.001conf 80SIGAQLXQL

  4. Behaviour (ATT&CK technique)

    Microsoft Defender protection disabled via Set-MpPreference (T1685)

    Requires Set-MpPreference together with a Disable* protection switch; exclusion management alone does not match. The value is not parsed — a re-enable ($false) also matches, so review before auto-response.

    APT2 · APT35 · APT5 · blackbyte · Contagious Interview · FIN6 · 21 more

    T1685conf 75SIGAQLXQL

  5. Behaviour (ATT&CK technique)

    AdFind domain trust or controller enumeration (T1482)

    Requires adfind plus a trust / DC enumeration switch; generic LDAP queries with other tools do not match.

    APT35 · blackbyte · Chimera · Earth Lusca · FIN8 · LOTUS PANDA · 4 more

    T1482conf 70SIGAQLXQL

  6. CVE exploitation

    CVE-2018-13379 exploitation attempt

    Keys on the distinctive part of the exploit request only (path traversal, exploit syntax in the query, an unusual parameter) — never on an endpoint the product serves in normal use. Needs raw request-URI logging (some web servers normalise ../ away). Scanners hitting the internet produce true-positive ATTEMPTS: correlate with sc-status / response size before declaring compromise.

    CVE-2018-13379 · APT29 · APT35 · DEV-0270 · ENERGETIC BEAR · Fox Kitten · lockbit · 3 more

    T1190conf 70SIGAQLXQL

  7. CVE exploitation

    CVE-2021-34473 exploitation attempt

    Keys on the distinctive part of the exploit request only (path traversal, exploit syntax in the query, an unusual parameter) — never on an endpoint the product serves in normal use. Needs raw request-URI logging (some web servers normalise ../ away). Scanners hitting the internet produce true-positive ATTEMPTS: correlate with sc-status / response size before declaring compromise.

    CVE-2021-34473 · APT35 · blackbyte · BRONZE STARLIGHT · Witchetty

    T1190conf 70SIGAQLXQL

  8. CVE exploitation

    CVE-2021-44228 exploitation attempt

    Keys on the distinctive part of the exploit request only (path traversal, exploit syntax in the query, an unusual parameter) — never on an endpoint the product serves in normal use. Needs raw request-URI logging (some web servers normalise ../ away). Scanners hitting the internet produce true-positive ATTEMPTS: correlate with sc-status / response size before declaring compromise.

    CVE-2021-44228 · APT35 · APT41 · BRONZE STARLIGHT · Sea Turtle · Water Sigbin

    T1190conf 70SIGAQLXQL

How to deploy

SIGSigma

  1. 1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
  2. 2.Run it as a hunt first: every rule ships as status experimental.
  3. 3.Promote to an alert once a week of results is clean on your data.

Check · The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.

AQLIBM QRadar

  1. 1.Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
  2. 2.Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
  3. 3.For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.

Check · Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.

XQLCortex XDR

  1. 1.Paste the XQL into Incident Response > Investigation > Query Builder > XQL Search.
  2. 2.To alert, save it as a Correlation Rule and set the MITRE tactic and technique printed with the rule.
  3. 3.Schedule it on the interval you hunt at; keep the fields stage for the alert's columns.

Check · CVE rules read PAN-OS URL logs (panw_ngfw_url_raw), which need the NGFW integration and, for HTTPS, decryption.