Sysmon for Linux

14 events across 1 channel

Event ID 1: Process Create

#
Provider
Sysmon for Linux

Description

A new process has been created. Provides the full command line, image path, process GUID, parent process information, and user context. Equivalent to Sysmon for Windows Event ID 1.

Fields #

NameDescriptionRules
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the created process
ProcessIdProcess ID of the created process
ImageFile path of the process being created449 detection rules
FileVersionVersion of the image associated with the process
DescriptionDescription of the image associated with the process
ProductProduct name the image belongs to
CompanyCompany name the image belongs to
OriginalFileNameOriginal file name
CommandLineArguments passed to the executable1768 detection rules
CurrentDirectoryCurrent working directory of the process4 detection rules
UserName of the user who created the process3 detection rules
LogonGuidLogon GUID of the user who created the process
LogonIdLogon ID of the user who created the process2 detection rules
TerminalSessionIdID of the terminal session
HashesHashes captured by Sysmon driver
ParentProcessGuidProcess GUID of the parent process
ParentProcessIdProcess ID of the parent process
ParentImageFile path of the parent process26 detection rules
ParentCommandLineArguments passed to the parent process executable22 detection rules
ParentUserName of the user who owns the parent process

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 1,
    "version": 5,
    "level": 4,
    "task": 1,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:01.467946000+00:00",
    "event_record_id": 2445127,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:01.468",
    "ProcessGuid": "{370e939b-1f99-6a38-b93b-fa0470630000}",
    "ProcessId": "313953",
    "Image": "/usr/bin/dash",
    "FileVersion": "-",
    "Description": "-",
    "Product": "-",
    "Company": "-",
    "OriginalFileName": "-",
    "CommandLine": "/bin/sh -c echo DWCAP1782062994_a aaa 'b b b' && true",
    "CurrentDirectory": "/home/debian",
    "User": "root",
    "LogonGuid": "{370e939b-0000-0000-0000-000000000000}",
    "LogonId": "0",
    "TerminalSessionId": "214",
    "IntegrityLevel": "no level",
    "Hashes": "SHA1=b03cf680f3ff9dc5d50cee5037bc03780e14f76f,MD5=623e332d8ae2db8a2d050dcce9510b47,SHA256=f5adb8bf0100ed0f8c7782ca5f92814e9229525a4b4e0d401cf3bea09ac960a6",
    "ParentProcessGuid": "{370e939b-1f99-6a38-9d2b-c87b445d0000}",
    "ParentProcessId": "313950",
    "ParentImage": "/usr/bin/bash",
    "ParentCommandLine": "bash",
    "ParentUser": "root"
  },
  "message": ""
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
CommandLinecontains/bin/sh11 rulessigma
CommandLinecontains/bin/bash8 rulessigma
CommandLinecontains/bin/zsh8 rulessigma
CommandLinecontains/bin/dash7 rulessigma
CommandLinecontains/bin/fish7 rulessigma
CommandLinecontains/tmp/7 ruleselastic, sigma
Imageends_with/curl9 rulessigma
Imageends_with/esxcli9 rulessigma
Imageends_with/cat8 rulessigma
Imageends_with/bash7 rulessigma
Imageends_with/head7 rulessigma
Imageends_with/more7 rulessigma
Imageends_with/tail7 rulessigma
Imageends_with/sh6 rulessigma
Imageends_with/wget6 rulessigma

Detection Rules #

View all rules referencing this event →

Sigma # view in coverage

  • Shell Invocation via Apt - Linux source medium: Detects the use of the "apt" and "apt-get" commands to execute a shell or proxy commands. Such behavior may be associated with privilege escalation, unauthorized command execution, or to break out from restricted environments.
  • Scheduled Task/Job At source low: Detects the use of at/atd which are utilities that are used to schedule tasks. They are often abused by adversaries to maintain persistence or to perform task scheduling for initial or recurring execution of malicious code
  • Audit Rules Deleted Via Auditctl source high: Detects the execution of 'auditctl' with the '-D' command line parameter, which deletes all configured audit rules and watches on Linux systems. This technique is commonly used by attackers to disable audit logging and cover their tracks by removing monitoring capabilities. Removal of audit rules can significantly impair detection of malicious activities on the affected system.
Show 17 more (141 total)
  • Kaspersky Endpoint Security Stopped Via CommandLine - Linux source high: Detects execution of the Kaspersky init.d stop script on Linux systems either directly or via systemctl. This activity may indicate a manual interruption of the antivirus service by an administrator, or it could be a sign of potential tampering or evasion attempts by malicious actors.
  • Suspicious Invocation of Shell via AWK - Linux source high: Detects the execution of "awk" or it's sibling commands, to invoke a shell using the system() function. This behavior is commonly associated with attempts to execute arbitrary commands or escalate privileges, potentially leading to unauthorized access or further exploitation.
  • Decode Base64 Encoded Text source low: Detects usage of base64 utility to decode arbitrary base64-encoded text
  • Linux Base64 Encoded Pipe to Shell source medium: Detects suspicious process command line that uses base64 encoded input for execution with a shell
  • Linux Base64 Encoded Shebang In CLI source medium: Detects the presence of a base64 version of the shebang in the commandline, which could indicate a malicious payload about to be decoded
  • Bash Interactive Shell source low: Detects execution of the bash shell with the interactive flag "-i".
  • Enable BPF Kprobes Tracing source medium: Detects common command used to enable bpf kprobes tracing
  • BPFtrace Unsafe Option Usage source medium: Detects the usage of the unsafe bpftrace option
  • Linux Setgid Capability Set on a Binary via Setcap Utility source low: Detects the use of the 'setcap' utility to set the 'setgid' capability (cap_setgid) on a binary file. This capability allows a non privileged process to make arbitrary manipulations of group IDs (GIDs), including setting its current GID to a value that would otherwise be restricted (i.e. GID 0, the root group). This behavior can be used by adversaries to backdoor a binary in order to escalate privileges again in the future if needed.
  • Linux Setuid Capability Set on a Binary via Setcap Utility source low: Detects the use of the 'setcap' utility to set the 'setuid' capability (cap_setuid) on a binary file. This capability allows a non privileged process to make arbitrary manipulations of user IDs (UIDs), including setting its current UID to a value that would otherwise be restricted (i.e. UID 0, the root user). This behavior can be used by adversaries to backdoor a binary in order to escalate privileges again in the future if needed.
  • Capabilities Discovery - Linux source low: Detects usage of "getcap" binary. This is often used during recon activity to determine potential binaries that can be abused as GTFOBins or other.
  • Capsh Shell Invocation - Linux source high: Detects the use of the "capsh" utility to invoke a shell.
  • Remove Immutable File Attribute source medium: Detects usage of the 'chattr' utility to remove immutable file attribute.
  • Chmod Targeting Sensitive Directories source medium: Detects chmod targeting files in sensitive directory paths on Linux systems. Attackers may use chmod to change permissions of files in these directories to maintain persistence, escalate privileges, or disrupt system operations.
  • Linux Sudo Chroot Execution source low: Detects the execution of 'sudo' command with '--chroot' option, which is used to change the root directory for command execution. Attackers may use this technique to evade detection and execute commands in a modified environment. This can be part of a privilege escalation strategy, as it allows the execution of commands with elevated privileges in a controlled environment as seen in CVE-2025-32463. While investigating, look out for unusual or unexpected use of 'sudo --chroot' in conjunction with other commands or scripts such as execution from temporary directories or unusual user accounts.
  • Linux Logs Clearing Attempts source medium: Detects logs clearing attempts on Linux systems via utilities such as 'rm', 'rmdir', 'shred', and 'unlink' targeting log files and directories. Adversaries often try to clear logs to cover their tracks after performing malicious activities.
  • Syslog Clearing or Removal Via System Utilities source high: Detects specific commands commonly used to remove or empty the syslog. Which is a technique often used by attacker as a method to hide their tracks

References #

Event ID 2: A process changed a file creation time

#
Provider
Sysmon for Linux

Description

A process explicitly modified a file creation time. Helps track the real creation time of files on Linux.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process that changed the file creation time
ProcessIdProcess ID of the process changing the file creation time
ImageFile path of the process that changed the file creation time
TargetFilenameFull path name of the file
CreationUtcTimeNew creation time of the file
PreviousCreationUtcTimePrevious creation time of the file
UserName of the user who changed the file creation time

References #

Event ID 3: Network connection

#
Provider
Sysmon for Linux

Description

A network connection was detected. Logs TCP/UDP connections with source and destination host, port, and process information.

Fields #

NameDescriptionRules
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process that made the network connection
ProcessIdProcess ID of the process that made the network connection
ImageFile path of the process that made the network connection1 detection rule
UserName of the user who owns the process
ProtocolNetwork protocol used (tcp or udp)
InitiatedWhether the process initiated the connection2 detection rules
SourceIsIpv6Whether the source address is IPv6
SourceIpSource IP address
SourceHostnameSource hostname
SourcePortSource port number
DestinationIsIpv6Whether the destination address is IPv6
DestinationIpDestination IP address2 detection rules
DestinationHostnameDestination hostname31 detection rules
DestinationPortDestination port number10 detection rules

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 3,
    "version": 5,
    "level": 4,
    "task": 3,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:02.050074000+00:00",
    "event_record_id": 2445208,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:02.057",
    "ProcessGuid": "{370e939b-1f9a-6a38-15b4-a15748570000}",
    "ProcessId": "313982",
    "Image": "/usr/bin/curl",
    "User": "root",
    "Protocol": "udp",
    "Initiated": "true",
    "SourceIsIpv6": "false",
    "SourceIp": "10.2.10.81",
    "SourceHostname": "-",
    "SourcePort": "1893",
    "SourcePortName": "-",
    "DestinationIsIpv6": "false",
    "DestinationIp": "10.2.10.254",
    "DestinationHostname": "-",
    "DestinationPort": "30817",
    "DestinationPortName": "-"
  },
  "message": ""
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Initiatedeqtrue2 rulessigma
DestinationHostnamecontainstunnel.ap.ngrok.com1 rulesigma
DestinationHostnamecontainstunnel.au.ngrok.com1 rulesigma
DestinationHostnamecontainstunnel.eu.ngrok.com1 rulesigma
DestinationHostnamecontainstunnel.in.ngrok.com1 rulesigma
DestinationHostnamecontainstunnel.jp.ngrok.com1 rulesigma
DestinationHostnamecontainstunnel.sa.ngrok.com1 rulesigma
DestinationHostnamecontainstunnel.us.ngrok.com1 rulesigma
DestinationHostnameends_with.localto.net1 rulesigma
DestinationHostnameends_with.localtonet.com1 rulesigma
DestinationHostnameeqca.minexmr.com1 rulesigma
DestinationHostnameeqde.minexmr.com1 rulesigma
DestinationHostnameeqfr.minexmr.com1 rulesigma
DestinationHostnameeqmine.c3pool.com1 rulesigma
DestinationHostnameeqmonerocean.stream1 rulesigma

Detection Rules #

View all rules referencing this event →

Sigma # view in coverage

Show 2 more (5 total)

References #

Event ID 4: Sysmon service state changed

#
Provider
Sysmon for Linux

Description

The Sysmon for Linux service state changed (started or stopped).

Fields #

NameDescription
UtcTimeTime in UTC when event was created
StateNew state of the Sysmon service (Started or Stopped)
VersionSysmon version
SchemaVersionSysmon configuration schema version

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 4,
    "version": 3,
    "level": 4,
    "task": 4,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:29:54.981574000+00:00",
    "event_record_id": 2445001,
    "correlation": {},
    "execution": {
      "process_id": 308429,
      "thread_id": 308429
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "UtcTime": "2026-06-21 17:29:54.981",
    "State": "Stopped",
    "Version": "1.5.1",
    "SchemaVersion": "4.90"
  },
  "message": ""
}

References #

Event ID 5: Process terminated

#
Provider
Sysmon for Linux

Description

A process has terminated. Logs the process GUID, PID, and image path of the terminated process.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the terminated process
ProcessIdProcess ID of the terminated process
ImageFile path of the terminated process
UserName of the user who owned the process

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 5,
    "version": 3,
    "level": 4,
    "task": 5,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:01.410643000+00:00",
    "event_record_id": 2445105,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:01.417",
    "ProcessGuid": "{370e939b-1f97-6a38-0936-d2a36d5e0000}",
    "ProcessId": "313921",
    "Image": "/usr/bin/sleep",
    "User": "root"
  },
  "message": ""
}

References #

Event ID 7: Shared library loaded

#
Provider
Sysmon for Linux

Description

A shared library (.so) was loaded into a process address space. Logs the image, loaded library path, and hash information.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process loading the library
ProcessIdProcess ID of the process loading the library
ImageFile path of the process loading the library
ImageLoadedFull path of the shared library loaded
FileVersionVersion of the loaded shared library
DescriptionDescription of the loaded shared library
ProductProduct name the shared library belongs to
CompanyCompany name the shared library belongs to
OriginalFileNameOriginal file name of the shared library
HashesHashes of the loaded shared library
SignedWhether the shared library is signed
SignatureSigner of the shared library
SignatureStatusStatus of the signature verification
UserName of the user who owns the process

References #

Event ID 9: RawAccessRead

#
Provider
Sysmon for Linux

Description

A process performed a raw read operation on a device. Useful for detecting attempts to read data outside the filesystem layer.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process performing raw access
ProcessIdProcess ID of the process performing raw access
ImageFile path of the process performing raw access
DeviceTarget device of the raw access read
UserName of the user who owns the process

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 9,
    "version": 2,
    "level": 4,
    "task": 9,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:02.704246000+00:00",
    "event_record_id": 2445239,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:02.708",
    "ProcessGuid": "{370e939b-1f9a-6a38-19e1-520a075c0000}",
    "ProcessId": "313994",
    "Image": "/usr/bin/dd",
    "Device": "/dev/vda",
    "User": "-"
  },
  "message": ""
}

References #

Event ID 10: Process accessed

#
Provider
Sysmon for Linux

Description

A process opened a handle to another process (for example to read or write its memory). Logs the source and target process, the granted access rights, and the call stack. Equivalent to Sysmon for Windows Event ID 10.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
SourceProcessGUIDProcess GUID of the source process that opened the target
SourceProcessIdProcess ID of the source process
SourceThreadIdThread ID within the source process that made the access
SourceImageFile path of the source process
TargetProcessGUIDProcess GUID of the target process being accessed
TargetProcessIdProcess ID of the target process
TargetImageFile path of the target process
GrantedAccessAccess rights the source process requested on the target
CallTraceStack trace at the point of access
SourceUserName of the user who owns the source process
TargetUserName of the user who owns the target process

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 10,
    "version": 3,
    "level": 4,
    "task": 10,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:03.138735000+00:00",
    "event_record_id": 2445252,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:03.145",
    "SourceProcessGUID": "{370e939b-1f9a-6a38-8912-6d0000000000}",
    "SourceProcessId": "313999",
    "SourceThreadId": "313999",
    "SourceImage": "/usr/bin/python3.11",
    "TargetProcessGUID": "{370e939b-1f9a-6a38-0956-aecb95590000}",
    "TargetProcessId": "314000",
    "TargetImage": "/usr/bin/sleep",
    "GrantedAccess": "0x0",
    "CallTrace": "-",
    "SourceUser": "root",
    "TargetUser": "root"
  },
  "message": ""
}

References #

Event ID 11: File created

#
Provider
Sysmon for Linux

Description

A file was created or overwritten. Logs the creating process and the target file path.

Fields #

NameDescriptionRules
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process that created the file
ProcessIdProcess ID of the process that created the file
ImageFile path of the process that created the file4 detection rules
TargetFilenameFull path of the created file85 detection rules
CreationUtcTimeCreation time of the file in UTC
UserName of the user who owns the process

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 11,
    "version": 2,
    "level": 4,
    "task": 11,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:02.011073000+00:00",
    "event_record_id": 2445205,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:01.995",
    "ProcessGuid": "{370e939b-1f99-6a38-b94b-810454620000}",
    "ProcessId": "313980",
    "Image": "/usr/bin/dash",
    "TargetFilename": "/tmp/DWCAP1782062994_nob",
    "CreationUtcTime": "2026-06-21 17:30:01.995",
    "User": "nobody"
  },
  "message": ""
}

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Imagecontains/python31 rulesigma
Imageends_with/curl1 rulesigma
Imageends_with/wget1 rulesigma
TargetFilenamecontains/etc/profile.d/1 rulesigma, splunk
TargetFilenameends_with.class1 rulesigma
TargetFilenameends_with.java1 rulesigma
TargetFilenameends_with.jsp1 rulesigma, splunk
TargetFilenameends_with.pth1 rulesigma
TargetFilenameends_with/etc/doas.conf1 rulesigma, splunk
TargetFilenameregex_match(?i)/lib/python3\.([5-9]|[0-9]{2})/site-packages/1 rulesigma
TargetFilenamestarts_with/tmp/1 ruleelastic, sigma
TargetFilenamestarts_with/var/tmp/1 ruleelastic, sigma

Detection Rules #

View all rules referencing this event →

Sigma # view in coverage

  • Linux Doas Conf File Creation source medium: Detects the creation of doas.conf file in linux host platform.
  • Persistence Via Sudoers.d Files source medium: Detects the creation or modification of files within the "sudoers.d" directory on Linux systems. Such activity may indicate an attempt to establish or maintain privilege escalation by granting specific users elevated permissions. Unauthorized changes to sudoers files are a common technique used by attackers to persist administrative access.
  • New Cron File Created source low: Detects the creation of cron files in Cron directories, which could indicate potential persistence mechanisms being established by an attacker. Note that not all cron file creations are malicious - legitimate system administration activities and software installations may also create cron files. This detection should be investigated in context, considering factors such as the user creating the file, the timing of creation, and the contents of the cron job. Focus investigation on unexpected cron files created by non-administrative users or during suspicious timeframes. Additionally, it is recommended to review the contents of the newly created cron files to assess their intent. Furthermore, it is suggested to baseline normal cron file creation and apply additional filters to reduce false positives based on the specific environment.
Show 14 more (17 total)
  • Suspicious Filename with Embedded Base64 Commands source high: Detects files with specially crafted filenames that embed Base64-encoded bash payloads designed to execute when processed by shell scripts. These filenames exploit shell interpretation quirks to trigger hidden commands, a technique observed in VShell malware campaigns.
  • Potentially Suspicious Shell Script Creation in Profile Folder source low: Detects the creation of shell scripts under the "profile.d" path.
  • Triple Cross eBPF Rootkit Default LockFile source high: Detects the creation of the file "rootlog" which is used by the TripleCross rootkit as a way to check if the backdoor is already running.
  • Triple Cross eBPF Rootkit Default Persistence source high: Detects the creation of "ebpfbackdoor" files in both "cron.d" and "sudoers.d" directories. Which both are related to the TripleCross persistence method
  • Wget Creating Files in Tmp Directory source medium: Detects the use of wget to download content in a temporary directory such as "/tmp" or "/var/tmp"
  • UNC4841 - Email Exfiltration File Pattern source high: Detects filename pattern of email related data used by UNC4841 for staging and exfiltration
  • UNC4841 - Barracuda ESG Exploitation Indicators source high: Detects file indicators as seen used by UNC4841 during their Barracuda ESG zero day exploitation.
  • Potential SAP NetWeaver Webshell Creation - Linux source medium: Detects the creation of suspicious files (jsp, java, class) in SAP NetWeaver directories, which may indicate exploitation attempts of vulnerabilities such as CVE-2025-31324.
  • Non-Standard Nsswitch.Conf Creation - Potential CVE-2025-32463 Exploitation source high: Detects the creation of nsswitch.conf files in non-standard directories, which may indicate exploitation of CVE-2025-32463. This vulnerability requires an attacker to create a nsswitch.conf in a directory that will be used during sudo chroot operations. When sudo executes, it loads malicious shared libraries from user-controlled locations within the chroot environment, potentially leading to arbitrary code execution and privilege escalation.
  • Shai-Hulud Malicious GitHub Workflow Creation source high: Detects creation of shai-hulud-workflow.yml file associated with Shai Hulud worm targeting NPM supply chain attack that exfiltrates GitHub secrets
  • Axios NPM Compromise File Creation Indicators - Linux source high: Detects file creation events linked to the Axios NPM supply chain compromise. Axios is a popular JavaScript HTTP client. On March 30, 2026, malicious versions (1.14.1, 0.30.4) were published to npm, injecting a dependency (plain-crypto-js@4.2.1) that executed a postinstall script as a cross-platform RAT dropper.
  • TeamPCP LiteLLM Supply Chain Attack Persistence Indicators source high: Detects the creation of specific persistence files as observed in the LiteLLM PyPI supply chain attack. In March 2026, a supply chain attack was discovered involving the popular open-source LLM framework LiteLLM by Threat Actor TeamPCP. The malicious package harvests every credential on the system, encrypts and exfiltrates them, and installs a persistent C2 backdoor.
  • Python Path Configuration File Creation - Linux source medium: Detects creation of a Python path configuration file (.pth) in Python library folders, which can be maliciously abused for code execution and persistence. Modules referenced by these files are run at every Python startup (v3.5+), regardless of whether the module is imported by the calling script. Default paths are '\lib\site-packages*.pth' (Windows) and '/lib/pythonX.Y/site-packages/*.pth' (Unix and macOS).
  • Potentially Suspicious Long Filename Pattern - Linux source low: Detects the creation of files with unusually long filenames (100 or more characters), which may indicate obfuscation techniques used by malware such as VShell. This is a hunting rule to identify potential threats that use long filenames to evade detection. Keep in mind that on a legitimate system, such long filenames can and are common. Run this detection in the context of threat hunting rather than alerting. Adjust the threshold of filename length as needed based on your environment.

References #

Event ID 16: Sysmon config state changed

#
Provider
Sysmon for Linux

Description

The Sysmon for Linux configuration was updated. Logs the new configuration hash.

Fields #

NameDescription
UtcTimeTime in UTC when event was created
ConfigurationName of the Sysmon configuration file
ConfigurationFileHashHash of the Sysmon configuration file

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 16,
    "version": 3,
    "level": 4,
    "task": 16,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:29:56.377582000+00:00",
    "event_record_id": 2445002,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "UtcTime": "2026-06-21 17:29:56.377",
    "Configuration": "/opt/sysmon/config.xml",
    "ConfigurationFileHash": "SHA1=827f50f67b592c10093ae52baa2b2c8b8472092c,MD5=826f4a072b7fd5787904d003ddc2748a,SHA256=8678f75b19b86da3d957f4eb76f894d6bb19737b7a404aa2d943588def9f795c"
  },
  "message": ""
}

References #

Event ID 22: DNS query

#
Provider
Sysmon for Linux

Description

A DNS query was issued by a process. Logs the queried domain name, query type, and query results.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process that issued the DNS query
ProcessIdProcess ID of the process that issued the DNS query
QueryNameDNS name queried
QueryTypeDNS query type (e.g. A, AAAA, CNAME)
QueryStatusStatus of the DNS query
QueryResultsResults of the DNS query
ImageFile path of the process that issued the DNS query
UserName of the user who owns the process

References #

Event ID 23: File Delete archived

#
Provider
Sysmon for Linux

Description

A file was deleted and an archived copy was preserved. Logs the process, target file, and hash information.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process that deleted the file
ProcessIdProcess ID of the process that deleted the file
UserName of the user who owns the process
ImageFile path of the process that deleted the file
TargetFilenameFull path of the deleted file
HashesHashes of the deleted file
IsExecutableWhether the deleted file was executable

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 23,
    "version": 5,
    "level": 4,
    "task": 23,
    "opcode": 0,
    "keywords": 9223372036854775808,
    "time_created": "2026-06-21T17:30:02.005258000+00:00",
    "event_record_id": 2445201,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:01.996",
    "ProcessGuid": "{370e939b-1f99-6a38-197a-b030e5640000}",
    "ProcessId": "313981",
    "User": "nobody",
    "Image": "/usr/bin/rm",
    "TargetFilename": "/tmp/DWCAP1782062994_nob",
    "Hashes": "-",
    "IsExecutable": "-",
    "Archived": "-"
  },
  "message": ""
}

References #

Event ID 100: BPF program activity

#
Provider
Sysmon for Linux

Description

An eBPF operation was observed via the bpf() syscall (for example BPF_PROG_LOAD). Logs the BPF command, program type, program id, and program name, plus the issuing process and user. Specific to Sysmon for Linux; no Sysmon for Windows equivalent.

Fields #

NameDescription
RuleNameCustom tag mapped to event
UtcTimeTime in UTC when event was created
ProcessGuidProcess GUID of the process issuing the BPF operation
ProcessIdProcess ID of the process issuing the BPF operation
ImageFile path of the process issuing the BPF operation
UserName of the user who owns the process
BpfCommandbpf() syscall command (for example BPF_PROG_LOAD)
BpfProgramTypeType of the eBPF program (for example SOCKET_FILTER)
BpfProgramIdKernel-assigned identifier of the eBPF program
BpfProgramNameName of the eBPF program

Example Event #

{
  "system": {
    "provider": "Linux-Sysmon",
    "guid": "{ff032593-a8d3-4f13-b0d6-01fc615a0f97}",
    "event_source_name": "",
    "event_id": 100,
    "version": 0,
    "level": 0,
    "task": 0,
    "opcode": 0,
    "keywords": 0,
    "time_created": "2026-06-21T17:30:03.188625000+00:00",
    "event_record_id": 2445256,
    "correlation": {},
    "execution": {
      "process_id": 313895,
      "thread_id": 313895
    },
    "channel": "Linux-Sysmon/Operational",
    "computer": "JD-debian-12-workstation",
    "security": {
      "user_id": "0"
    }
  },
  "event_data": {
    "RuleName": "-",
    "UtcTime": "2026-06-21 17:30:03.176",
    "ProcessGuid": "{370e939b-1f9b-6a38-8912-6d0000000000}",
    "ProcessId": "314001",
    "Image": "/usr/bin/python3.11",
    "User": "root",
    "BpfCommand": "BPF_PROG_LOAD",
    "BpfProgramType": "SOCKET_FILTER",
    "BpfProgramId": "3",
    "BpfProgramName": "dwcap1782062994"
  },
  "message": ""
}

References #

Event ID 255: Error

#
Provider
Sysmon for Linux

Description

Sysmon for Linux encountered an error. Logged when the driver or service encounters an unexpected condition.

Fields #

NameDescription
UtcTimeTime in UTC when the error occurred
IDEvent ID that encountered the error
DescriptionDescription of the error

References #