Join our Newsletter — 33% off our NHI Course
Home› Guides› IOC Scanners Guide: THOR Lite, LOKI and safe…
Guide SOC & Detection Engineering

IOC Scanners Guide: THOR Lite, LOKI and safe compromise sweeps

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 8 November 2026 11 min read
On this page

When an advisory drops with hashes, file names and YARA rules, most teams cannot quickly answer the only question that matters: is this on any of our machines right now? IOC scanners answer it. They are portable, agentless tools that sweep a host's file system and process memory for YARA matches, known bad hashes, suspicious file name patterns and connections to known command and control addresses, and produce a scored report. This guide covers the best-known free options from the same author and vendor family: LOKI (Python, now deprecated), LOKI RS (its Rust rewrite), Fenrir (a Bash scanner for Unix) and THOR Lite (Nextron Systems' free edition of its commercial THOR scanner), plus the signature sources behind them. It is for incident responders, SOC analysts and compromise assessment teams. Writing the rules themselves is covered in the YARA Rules Guide; this page is about running sweep scanners safely and getting value from the results.

This is an independent guide from NHI Mgmt Group, based on Nextron Systems's public documentation as of November 2026. It is not sponsored or reviewed by Nextron Systems. Product features change, so confirm settings against Nextron Systems's current documentation.

Key takeaways

  • They answer "are we affected?" fast. A scanner copied to a host, or run from a share, checks files and memory against current indicators without installing an agent, which suits incident triage and third-party environments without EDR.
  • Choose the maintained tool. The LOKI (Python) repository states it is deprecated and in inactive maintenance; its author points users to LOKI RS (beta) or THOR Lite.
  • Licences differ and matter. LOKI and LOKI RS are GPL-3.0; the signature-base rules are under the Detection Rule License 1.1; THOR Lite is free but not open source, and Nextron requires THOR Enterprise for use on third-party networks or in paid engagements.
  • Signatures go stale in days. LOKI RS warns that bundled signatures get stale quickly; update before every sweep and add the indicators from the advisory you are responding to.
  • Results are leads, not verdicts. Scores (notice, warning, alert) prioritise review; every hit needs analyst triage, and a clean sweep only means none of the loaded indicators matched.

What the tool does

All four scanners follow the same pattern: load a set of indicators, walk the file system and, where supported, read process memory, then score each finding and write a log.

Detection methodHow it worksWhere documented
YARA rulesSignature match on file contents and process memory.LOKI, LOKI RS (using yara-x), THOR Lite
Hash IOCsMD5, SHA1 or SHA256 of scanned files compared with known bad hashes.LOKI, LOKI RS, Fenrir, THOR Lite
File name IOCsRegular expression on the full path, with an optional score and false positive regex (LOKI format: regex;score;fp-regex).LOKI, LOKI RS; Fenrir uses substring match
C2 IOCsProcess connection endpoints compared with C2 indicators (Fenrir reads lsof output).LOKI, LOKI RS, Fenrir
Hot time frameLists files created between two epoch timestamps.Fenrir
Process integrityPE-Sieve checks for in-memory tampering on Windows.LOKI (optional flags), THOR Lite per Nextron's comparison

The scanners compared

ScannerStatus and licencePlatformsNotable points
LOKIDeprecated, inactive maintenance; GPL-3.0Windows binary (PyInstaller); Linux and macOS from sourceClear-text signatures from signature-base; user excludes in config/excludes.cfg; GREEN, YELLOW or RED result line.
LOKI RSBeta, active development; GPL-3.0Pre-compiled releases per platformMulti-threaded single binary; YARA Forge Core rules by default; JSONL, HTML report, syslog (UDP or TCP); CPU limit and thread controls; default thresholds alert 80, warning 60, notice 40.
FenrirBash script; actively developed per its repositoryLinux, Unix, macOS with BashNo install; uses md5sum, grep, stat and lsof; designed for many Linux hosts via an Ansible playbook using a RAM drive.
THOR LiteFree, registration required, not open sourceWindows, Linux, macOSGo scanner; about 4,000 open source YARA rules from signature-base shipped encrypted; SYSLOG and JSON output over UDP, TCP or file; Nextron private rules and technical support come with commercial THOR.

Check the vendor page before you rely on a feature: Nextron's THOR Lite product page and its scanner comparison page describe the module set differently (for example on event log and Sigma processing), so confirm the current capability in the manual and release notes for the version you deploy.

Defender use cases

  • Advisory response sweeps: load the YARA rules and hashes from a new advisory, such as the YARA rules NSA published for APT5 activity on Citrix ADC, and sweep the relevant server class within hours. See the APT5 Threat Actor Profile Guide.
  • Compromise assessment: run across a representative sample of hosts to look for known tooling, web shells and implants before or after an acquisition. Combine with log review and hunting as described in the Compromise Assessment Guide.
  • Triage during an incident: scan suspected hosts and their neighbours to scope spread, and scan mounted disk images offline (LOKI RS documents a --no-procs --folder pattern for mounted images).
  • Coverage where EDR is missing: legacy servers, OT jump hosts, appliances with a Linux shell, or a supplier's environment during joint response (subject to licence terms).
  • Web server checks: sweep web roots for web shells after an internet-facing exploit, a recurring step in edge and Exchange incidents.
  • Validating detections: confirm a rule set fires on a known sample in the lab before trusting a clean result in production.

Deployment and safe use

Rollout steps

  1. Pick and verify the build. Download only from the project's GitHub releases or the vendor portal, check the published hashes or signatures, and record the version used for the case file.
  2. Update signatures on a connected system. LOKI uses loki-upgrader.exe, LOKI RS uses loki-util update, THOR Lite ships an update utility. Then add your case-specific IOC files (file names containing "hash", "filename" or "c2" in the LOKI family's iocs folder).
  3. Pilot on non-critical hosts. Measure run time, CPU and I/O on a typical server and workstation, and review false positives before a wide sweep.
  4. Coordinate with EDR and antivirus. Scanners carry malware signatures and read process memory, so endpoint protection may quarantine the rule files or block the scanner. Add a narrow, time-limited exclusion for the scanner path and hash, and remove it after the sweep. See the EDR Tuning and Exclusions Management Guide.
  5. Run with the right privilege. LOKI's documentation notes some checks are disabled and files inaccessible without administrator rights. Run elevated only for the duration of the scan, from a dedicated response account.
  6. Throttle production systems. Use LOKI RS --cpu-limit and --threads, or THOR's CPU limit, and schedule database and file servers outside peak hours. Exclude database and replication paths: the LOKI sample excludes.cfg lists \Ntds\, \Ntfrs\ and Sysvol staging.
  7. Centralise the output. Send results to the SIEM over syslog or JSON (LOKI RS --remote with --remote-format json) so findings across hundreds of hosts can be sorted by score.
  8. Clean up. Remove the binary, signatures and any temporary exclusions; keep the logs with the case evidence.

Safety and data handling

  • Stability: process memory scanning is the riskiest part. LOKI RS skips device-backed mappings on Linux and offers --no-procs; the THOR manual describes resource control that stops a scan when free physical memory falls below 50 MB and an automatic soft mode on hosts with fewer than 2 cores or under 1024 MB RAM.
  • Do not upload confidential samples: LOKI's README suggests VirusTotal for non-confidential samples only. Hits on internal documents or proprietary binaries stay inside the organisation.
  • Network shares and cloud folders: LOKI RS skips network, mounted and cloud storage directories unless --scan-all-drives is set. Do not enable it on a file server sweep without the share owner's agreement and a load plan.
  • Evidence integrity: scanners read every file and update access times on some file systems. Image first when the host may become evidence; see the Disk Imaging and Forensic Acquisition Guide.
  • Licensing: THOR Lite's terms permit government, education and research and internal company use; Nextron states that use on third-party networks or as part of a paid engagement needs THOR Enterprise. The signature-base rules are under DRL 1.1 except rules whose metadata states another licence. Consultancies should check both before a client engagement.

Where identity fits

The response account used to push and run scanners across the estate is a powerful credential: local administrator or root on every scanned host. Use a dedicated account, issue it through just-in-time elevation, avoid interactive logons that leave reusable credentials on suspect machines, and disable it after the sweep. A compromised scanner account would hand an attacker the same reach as the responders. See the Privileged Access Management Guide.

Detection and hardening value

Treat the scanner as one input. Its value is in fast, repeatable coverage of known indicators, and in feeding new detections back into always-on tooling.

Score bandLOKI RS defaultTHOR manualSuggested handling
Notice4040 or aboveBatch review; use for hunting context.
Warning6060 or aboveAnalyst review within the shift.
Alert80Above 80, with at least one sub score above 75Immediate triage; consider isolating the host.
  • Triage each hit: read the matching rule and its reference, check the file's signer, path and age, and compare with the host's role. Report false positives upstream (the projects ask for the rule name and hash or file name) and add local exclusions with a reason.
  • Feed detection engineering: a confirmed match should become an EDR or SIEM detection so the next occurrence is caught without a sweep. Convert behaviours into Sigma Rules where possible.
  • Close the gap that allowed it: a web shell found on an appliance or IIS host is a patching and exposure failure as well as a detection one.

Framework mapping: sweeps support NIST SP 800-53 SI-3 (Malicious Code Protection), RA-10 (Threat Hunting) and IR-4 (Incident Handling), and CSF 2.0 DE.CM-09, DE.AE-02 and RS.AN-03. In MITRE D3FEND terms they implement File Analysis (D3-FA), File Hashing (D3-FH) and Process Analysis (D3-PA).

Metrics: time from advisory publication to completed sweep of in-scope hosts; percentage of in-scope hosts successfully scanned (not just attempted); false positive rate per sweep; percentage of confirmed hits converted into a standing EDR or SIEM detection within 7 days; age of signatures at scan time (target under 24 hours).

Alternatives

OptionStrengthTrade-off
EDR live response and YARA scanningAlready deployed, central, auditable.Only covers enrolled hosts; feature depth varies by product.
VelociraptorOpen source DFIR agent with YARA and artefact collection at scale.Needs a server and agent deployment.
osquerySQL queries across a fleet, including file hashes and YARA tables.Requires the agent and query design effort.
Commercial THORPrivate rules, Sigma content, forensic artefact parsing, lab and remote modes, support.Paid licence.
Plain YARA or yara-x CLISimplest, fully transparent.No hash, file name or C2 checks, no scoring or reporting.

Small teams without EDR coverage gain most from a portable scanner kept ready in the incident toolkit. Large estates should run sweeps through their EDR or a DFIR platform for audit and scale, and keep a portable scanner for unmanaged or third-party systems.

Practitioner checklist

  • Standardise on a maintained scanner (LOKI RS or THOR Lite) and retire LOKI (Python) builds from the toolkit.
  • Confirm licence terms for your use case, especially consultancies and managed service providers.
  • Keep a verified build and an update procedure documented in the incident response runbook.
  • Pre-agree temporary EDR exclusions and the response account used to run sweeps.
  • Pilot on each server class and record safe CPU, thread and exclusion settings.
  • Update signatures and load case-specific IOCs before every sweep.
  • Ship results to the SIEM and triage by score with a documented SLA.
  • Convert confirmed findings into standing detections and report false positives upstream.

Standards and references

Related NHI Mgmt Group resources: YARA Rules Guide · Compromise Assessment Guide · Threat Hunting Guide · Digital Forensics (DFIR) Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 8 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.