Linux VSFTPD Logs: Suspicious Error Messages Indicating Possible Exploitation Attempts

Looks for specific vsftpd error strings that may indicate exploitation-triggered faults or abnormal request handling.

FreeReviewedSigma · Medium · v3
Product
linux
Service
vsftpd
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-07-05
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags VSFTPD log entries containing specific error messages that reflect fatal or suspicious conditions often triggered during exploitation attempts. Attackers may provoke these states by sending malformed inputs, conflicting session parameters, or unexpected protocol/HTTP data to stress error handling paths. The detection relies on Linux VSFTPD service log events matching the listed keyword strings.

Related detections9 linkedT1190 — drag to rearrange
ToolShell SharePoint CVE-2025-53770 Exploitation via ToolPane Endpoint With SignOut Referer (via webserver)
Malicious Next.js Node Process Spawning Shell Downloader after RSC Deserialization RCE (via process_creation)
SharePoint ToolShell Exploitation via ToolPane POST with SignOut Referer (via webserver)
Possible OMIGOD Unauthenticated OMI WSMan Command Execution via Web Request (via webserver)
Suspicious Spring Boot Actuator Heapdump and Gateway SSRF Access via Webserver
Possible Ivanti EPMM Expression Language Injection on FeatureUsage Endpoint (CVE-2025-4427)
Suspicious Node.js Fileless Webshell Magic Path Request via Webserver
Suspicious Ollama api pull Path Traversal Request (CVE-2024-37032)
Malicious Git Config sshCommand Modification for Code Execution on Linux
Linux VSFTPD Logs: Suspicious Error Messages Indicating Possible Exploitation Attempts
Pivot detection · T1190 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. 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.