interlock_ransomware

[tccontre]

Tagged

Windows PowerShell FakeCAPTCHA Clipboard Execution
Windows Multi hop Proxy TOR Website Query
TOR Traffic
Windows Boot or Logon Autostart Execution In Startup Folder
System Information Discovery Detection
Network Connection Discovery With Arp
Remote Desktop Network Traffic
Windows RDPClient Connection Sequence Events
Windows RDP File Execution
Windows RDP Connection Successful
Enable RDP In Other Port Number
Cisco Secure Firewall - Remote Access Software Usage Traffic
Detect Remote Access Software Usage DNS
Detect Remote Access Software Usage Traffic
Detect Remote Access Software Usage URL
Detect Remote Access Software Usage File
Detect Remote Access Software Usage Process
Detect Remote Access Software Usage FileInfo
Registry Keys Used For Persistence
Windows AD ServicePrincipalName Added To Domain Account
Disabled Kerberos Pre-Authentication Discovery With Get-ADUser
Windows AD Short Lived Domain Account ServicePrincipalName
Windows PowerView SPN Discovery
Disabled Kerberos Pre-Authentication Discovery With PowerView
Domain Account Discovery with Wmic
Ransomware Notes bulk creation
Windows Suspicious Process File Path
Windows Suspicious Driver Loaded Path
Executables Or Script Creation In Suspicious Path
High Process Termination Frequency
PowerShell Domain Enumeration
PowerShell 4104 Hunting
Windows High File Deletion Frequency
windows_unsigned_dll_side_loading_in_same_process_path.yml

lookups

common_ransomware_extensions.yml
common_ransomware_notes.yml
ansomware_extensions_lookup.csv
ransomware_notes_lookup.csv

new detection

Windows Rundll32 Load DLL in Temp Dir

new story

• interlock_rat.yml
• interlock_ransomware.yml
• nailoaolocker_ransomware.yml

What does this PR have in it? Screenshots are worth 1000 words 😄

Checklist

• Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
• CI/CD jobs passed ✔️
• Validated SPL logic.
• Validated tags, description, and how to implement.
• Verified references match analytic.
• Confirm updates to lookups are handled properly.

Notes For Submitters and Reviewers

• If you're submitting a PR from a fork, ensuring the box to allow updates from maintainers is checked will help speed up the process of getting it merged.
• Checking the output of the build CI job when it fails will likely show an error about what is failing. You may have a very descriptive error of the specific field(s) in the specific file(s) that is causing an issue. In some cases, its also possible there is an issue with the YAML. Many of these can be caught with the pre-commit hooks if you set them up. These errors will be less descriptive as to what exactly is wrong, but will give you a column and row position in a specific file where the YAML processing breaks. If you're having trouble with this, feel free to add a comment to your PR tagging one of the maintainers and we'll be happy to help troubleshoot it.
• Updates to existing lookup files can be tricky, because of how Splunk handles application updates and the differences between existing lookup files being updated vs new lookups. You can read more here but the short version is that any changes to lookup files need to bump the the date and version in the associated YAML file.