← Back to SOC feed Coverage →

ThreatFox: NjRAT IOCs

ioc-hunt HIGH ThreatFox
DeviceFileEvents
backdooriocthreatfoxwin-njrat
This rule was pulled from an open-source repository and enriched with AI. Validate in a test environment before deploying to production.
View original rule at ThreatFox →
Retrieved: 2026-07-10T23:00:00Z · Confidence: high

Hunt Hypothesis

This hunt targets adversary behavior involving NjRAT malware by identifying network connections and process executions matching three specific Indicators of Compromise (IOCs). Proactively hunting for these signatures in Azure Sentinel is critical to detect early-stage remote access tool deployments that could establish persistent command-and-control channels within the enterprise environment.

IOC Summary

Malware Family: NjRAT Total IOCs: 3 IOC Types: md5_hash, sha256_hash, sha1_hash

TypeValueThreat TypeFirst SeenConfidence
sha1_hash2e70ac7f1bdfc2f9912448ee2b6c2c478bef3aabpayload2026-07-1095%
md5_hash1b622c451fcc9d83aad8bf45b1c42b5fpayload2026-07-1095%
sha256_hashdf4e36252bf8a2b1dee291bcaf9e0505246cacc1d1ea9db3494f30c8506ba0cbpayload2026-07-1095%

KQL: Hash Hunt

// Hunt for files matching known malicious hashes
// Source: ThreatFox - NjRAT
let malicious_hashes = dynamic(["2e70ac7f1bdfc2f9912448ee2b6c2c478bef3aab", "1b622c451fcc9d83aad8bf45b1c42b5f", "df4e36252bf8a2b1dee291bcaf9e0505246cacc1d1ea9db3494f30c8506ba0cb"]);
DeviceFileEvents
| where SHA256 in (malicious_hashes) or SHA1 in (malicious_hashes) or MD5 in (malicious_hashes)
| project Timestamp, DeviceName, FileName, FolderPath, SHA256, InitiatingProcessFileName
| order by Timestamp desc

Required Data Sources

Sentinel TableNotes
DeviceFileEventsEnsure this data connector is enabled

References

False Positive Guidance

Here are specific false positive scenarios for the ThreatFox: NjRAT IOCs detection rule, including suggested filters and exclusions tailored for an enterprise environment:

Original source: https://threatfox.abuse.ch/browse/malware/win.njrat/