huntrule

Suspicious Registry Import of Nimbus RAT Configuration via Regedit

PremiumReviewedSigma · High · v1
Category
process_creation
Author
HuntRule
Published
2026-09-22
Updated
2026-09-22
AnalysisDetection

ATT&CK techniques

Persistence → Defense Evasion

  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 detects regedit.exe silently importing an InboxCorePro registry file, a step the Nimbus RAT uses to apply its configuration and persistence keys. The reg file is dropped alongside the Java payload in the ProgramData install directory. Automated registry imports referencing the malware family name indicate implant setup.

Reporting behind it

Related detections9 linkedT1112 — drag to rearrange
Suspicious RiseLoader Infection Marker Registry Key (via registry_set)
Suspicious OneNote Embedded File Open Warning Disabled via Registry
Malicious WDigest UseLogonCredential Cleartext Credential Enablement
Suspicious Run Key Persistence via Reg Add
Malicious Task Manager Disabling via DisableTaskMgr Policy Registry Value
Suspicious Registry Value under Console WindowsUpdates for C2 Storage
Suspicious Office VBA Object Model Access Enabled via Registry (via registry_set)
Suspicious PowerShell Payload Staging in HKCU Printers Registry Key
Suspicious Rootkit Configuration Registry Keys (via registry_set)
Suspicious Registry Import of Nimbus RAT Configuration via Regedit
Pivot detection · T1112 · 9 related

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