T1587 IBM QRadar · QRadar

Detect Develop Capabilities in IBM QRadar

This detection identifies indicators that adversaries have deployed custom-developed capabilities within the target environment. Because T1587 (Develop Capabilities) occurs outside the victim network during the adversary lifecycle, direct detection is impossible; instead, this rule focuses on second-order indicators: unsigned or self-signed executables executing from non-standard paths, low-prevalence binaries making network connections, and novel tooling patterns associated with bespoke malware frameworks. Groups such as Kimsuky, Moonstone Sleet, and Contagious Interview are known to develop custom tools—including malicious NPM packages, spearphishing toolkits, and custom implants—that exhibit these characteristics upon deployment. The detection correlates signature anomalies, environmental prevalence, and behavioral signals to surface likely custom-developed tools used in targeted intrusions.

MITRE ATT&CK

Tactic
Resource Development
Technique
T1587 Develop Capabilities
Canonical reference
https://attack.mitre.org/techniques/T1587/

QRadar Detection Query

IBM QRadar (QRadar)
sql
SELECT
  DATEFORMAT(starttime, 'YYYY-MM-dd HH:mm:ss') AS EventTime,
  sourceip,
  username,
  QIDNAME(qid) AS EventName,
  "Process Name" AS ProcessName,
  "Process Path" AS ProcessPath,
  "File Hash" AS SHA256Hash,
  "Signature Status" AS SignatureStatus,
  destinationip,
  destinationport,
  logsourceid,
  CATEGORYNAME(category) AS Category
FROM events
WHERE
  LOGSOURCETYPEID(devicetype) IN (
    SELECT id FROM logsourcetypes WHERE name LIKE '%Sysmon%' OR name LIKE '%Windows%'
  )
  AND (
    (qid = 5145670 AND "Signed" = 'false')  -- Sysmon EventCode 7 ImageLoad unsigned
    OR
    (qid = 5145664  -- Sysmon EventCode 1 ProcessCreate
      AND (
        "Process Path" ILIKE '%\\AppData\\Local\\Temp\\%'
        OR "Process Path" ILIKE '%\\Downloads\\%'
        OR "Process Path" ILIKE '%\\ProgramData\\%'
        OR "Process Path" ILIKE 'C:\\Temp\\%'
        OR "Process Path" ILIKE 'C:\\Windows\\Temp\\%'
      )
      AND "Process Path" NOT ILIKE '%\\Windows\\System32\\%'
      AND "Process Path" NOT ILIKE '%\\Program Files%'
    )
  )
  AND starttime > NOW() - 86400000
GROUP BY sourceip, username, ProcessPath, SHA256Hash, SignatureStatus
HAVING COUNT(DISTINCT sourceip) < 5
ORDER BY EventTime DESC
LIMIT 500
high severity medium confidence

Detects unsigned or invalidly-signed executables running from non-standard user-writable paths on Windows endpoints via Sysmon event codes 1 and 7 ingested into QRadar. Filters to low-prevalence binaries (fewer than 5 unique hosts) to surface likely custom-developed tools. Uses AQL aggregate grouping over a 24-hour lookback window.

Data Sources

IBM QRadar with Windows Sysmon DSMMicrosoft Windows Sysmon logs via QRadar WinCollect agent

Required Tables

events

False Positives & Tuning

  • Legitimate portable utilities executed from user download directories on low-user-count hosts
  • Internal tooling deployed to a small subset of endpoints during staged rollouts
  • Pentest or red team tooling executed from temp paths during authorised engagements
Download portable Sigma rule (.yml)

Other platforms for T1587


Testing Methodology

Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Execute Self-Signed Binary from User-Writable Path (Windows)

    Expected signal: DeviceProcessEvents: FileName=custom_capability_test.exe, ProcessSignatureStatus=SignedByUntrustedCertificate, FolderPath contains \AppData\Local\Temp. DeviceImageLoadEvents showing DLLs loaded with self-signed parent process.

  2. Test 2Deploy Malicious NPM Post-Install Script (Cross-Platform)

    Expected signal: Sysmon EventCode=1 (Linux auditd execve): process spawned with ParentImage=/usr/bin/node, Image=/bin/sh or /bin/id. audit.log entries showing execve syscall from node process with working directory in node_modules path.

  3. Test 3Compile and Execute Custom ELF Binary with Network Connection (Linux)

    Expected signal: auditd: EXECVE record for /tmp/atomic_custom_tool with ppid matching shell. SOCKADDR audit record showing connect() call to 192.0.2.1:4444. Sysmon for Linux EventCode=3 (Network Connect) if deployed. /proc/<pid>/exe pointing to /tmp path.

Unlock Pro Content

Get the full detection package for T1587 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections