Detections

Explore public detection logic contributed by the community across SIEM and rule languages.

5 detections

Detects the execution of JavaScript files using wscript.exe from user-writable directories (e.g., Temp, Downloads, AppData) that exhibit high levels of obfuscation. The rule specifically flags scripts containing a high ratio of comment lines to code, a technique often used in the LausivLoader malware family to mask malicious payloads constructed using String.fromCharCode.
avatar
Ibrahim Saud@tektrix
avatar
Detections.ai Community
1 month ago
003
This rule detects the delivery of a payload via HTTP that contains junk code padding and appears to be an executable file. Specifically, it looks for the byte sequence '90 90 90 90 90 90 90 90 90 90' (often used as NOPs for padding or obfuscation) followed by the 'MZ' magic bytes at the beginning of a file (indicating a Windows executable). The detection is triggered on HTTP responses flowing to the client.
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
5 months ago
008
Detects NOP sled patterns in payloads indicating junk code insertion for evasion
avatar
Darshan Thummar@Mighty
avatar
Detections.ai Community
5 months ago
104
'The query looks for source code files being modified immediately after a build process is started. The purpose of this is to look for malicious code injection during the build process.
More details: https://techcommunity.microsoft.com/t5/azure-sentinel/monitoring-the-software-supply-chain-with-azure-sentinel/ba-p/2176463'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
2075
'Potential code injection into web server roles via IIS logs scan. Represents attempt to gain initial access using drive-by compromise technique. Detection flags events for review and filtering of authorized activity.'
Azure Sentinel@AzureSentinel
avatar
AzureSentinel
1 year ago
1071