huntrule

Python SQL Exception Errors Indicating Database Interaction Failures

Identifies Python application logs referencing common SQL exception classes from DB-API (PEP 249).

FreeReviewedSigma · Medium · v5
Product
python
Category
application
Author
Thomas Patzke (SigmaHQ), DRL 1.1
Published
2017-08-12
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Initial Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags application events from Python that include SQL-related exception class names tied to common database error categories: DataError, IntegrityError, ProgrammingError, and OperationalError. Attackers may intentionally trigger or probe database behavior to test inputs, validate states, or reach deeper application code paths. The detection relies on application telemetry that contains these exception keywords in the emitted log text.

Reporting behind it

Related detections9 linkedT1190 — drag to rearrange
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Malicious Command Shell or PowerShell Spawned by Tomcat via Process Creation (via process_creation)
Suspicious Shell Script Execution From Temp Directory on SonicWall SMA1000 Appliance (via process_creation)
Possible TP-Link Command Injection via WlanNetworkRpm Endpoint (via webserver)
Malicious SharePoint ToolPane Exploitation via SignOut Referer
Suspicious Tomcat Session Deserialization Trigger via Crafted JSESSIONID
Malicious Tomcat Partial PUT of Session File via Content-Range Header
Malicious Ivanti Connect Secure Path Traversal Exploitation of CVE-2024-21887
Malicious MOVEit moveitisapi Exploitation Request via webserver
Python SQL Exception Errors Indicating Database Interaction Failures
Pivot detection · T1190 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.