Is NatroMacro-fix(1).zip safe?
Only 4 of 74 engines detected the archive, but one tier-1 alert, defense-evasion activity, and an incompletely resolved child set warrant caution.
The detections are sparse and inconsistent: 4 of 74 engines flagged the archive, with only Fortinet contributing a tier-1 alert. Runtime evidence includes defense-evasion activity and direct-IP traffic, but no malicious sandbox conclusion or known-malicious child was recorded; avoid running it until its source and extracted files are independently verified.
5434b6ace7df73b6c0…60e3cce5e51dfdRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
The detections are sparse and inconsistent: 4 of 74 engines flagged the archive, with only Fortinet contributing a tier-1 alert. Runtime evidence includes defense-evasion activity and direct-IP traffic, but no malicious sandbox conclusion or known-malicious child was recorded; avoid running it until its source and extracted files are independently verified.
Four of 74 engines flagged the archive, but their labels do not converge on a specific family. Fortinet supplied the only tier-1 alert, while the other 16 tier-1 engines did not detect it. One sandbox run observed T1562.001 and direct-IP traffic, although it produced no malicious runtime conclusion or persistence indicator. The complete host cross-check found no complete contacted-host reputation result was available, but one observed GitHub content host carried a suspicious reputation entry. None of the ten inspected children was identified as malicious, yet all ten lack completed individual verdicts, leaving material uncertainty. Research feeds and rules provided no independent family corroboration.
What We Detected
Four of 74 antivirus engines flagged the ZIP archive. Fortinet reported W32/PossibleThreat, VirIT reported GenusT.FWRX, Zillya reported AdWrapper, and VBA32 supplied a phishing heuristic; this disagreement does not establish a single malware family. Fortinet was the only tier-1 detector, while 16 other tier-1 engines did not detect the sample.
Threat Behavior
One completed sandbox run observed T1562.001, command-script and AutoHotkey execution, and traffic to four external IP addresses. It did not produce a malicious sandbox conclusion or persistence indicators. Reputation checks covered all four contacted IPs and found none known malicious, though raw.githubusercontent.com was marked suspicious; the recorded requests targeted GitHub project resources and certificate-revocation infrastructure. Ten extracted children were inspected without a malicious finding, but each still lacks an individual verdict.
What To Do Now
Do not execute the archive on a primary system until its download source and SHA-256 are confirmed against the project's official release channel. Keep endpoint protection enabled, scan the extracted contents separately, and use an isolated test environment if execution is necessary.
Where this verdict could be wrong3 caveats
- Fortinet, a tier-1 engine, reported W32/PossibleThreat, so the detections cannot be dismissed as low-trust-only noise.
- Runtime observation included T1562.001 and four direct IP contacts, which can indicate defense evasion or command-and-control despite the absence of a malicious sandbox verdict.
- The ten dropped children have no completed individual verdicts, so hasMaliciousChild=false does not establish that every extracted component is benign.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 4/74 engines detected the archive, and 16/17 tier-1 engines did not.
- behaviour.hasMaliciousSandboxVerdict=false after one completed run.
- contactedHosts found 0 known-malicious hosts across all four contacted IPs.
- droppedChildren.hasMaliciousChild=false for 10 inspected hashes.
- YARAify, MalwareBazaar, and CIRCL returned no corroborating hits.
- Fortinet supplied 1 tier-1 detection among 74 engines.
- Runtime observation included MITRE T1562.001.
- The DirectIpC2 heuristic recorded four external IP contacts.
- raw.githubusercontent.com was marked suspicious by the contacted-host cache.
- All 10 extracted child files remain individually unclassified.
- The archive contains executable and script components launched from a temporary directory.
Quarantine the archive pending source verification and separate scanning of every extracted component. Keep endpoint protection enabled and execute only in an isolated environment if testing is essential.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial4 of 8 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 8MITRE ATT&CK techniques
- 15spawned processes
- 9network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
NatroMacro-fix(1).zip
5434b6ace7df73b6c025f7e2c59523f0813bb9c79e1e61c51360e3cce5e51dfd
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset/nm_image_assets/Styles/USkin.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset/START.bat^"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Heartbeat.ahk
C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\submacros\Heartbeat.ahk
04Isolated runtime analysis - Written fileObserved
patternHashes.ahk
C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\settings\imported\patternHashes.ahk
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
raw.githubusercontent.com
Saved reputation verdict: suspicious.
06Contacted-host cross-check - Contacted hostObserved
140.82.114.5
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 140.82.114.5
- 185.199.109.133
- 23.195.81.176
- 104.18.20.213
- http://yr.c.lencr.org/
- http://yr2.c.lencr.org/30.crl
- https://api.github.com/repos/NatroTeam/NatroMacro/releases
- https://raw.githubusercontent.com/NatroTeam/.github/main/data/contributors.txt
- https://raw.githubusercontent.com/NatroTeam/.github/main/data/beesmas.txt
- C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\submacros\Heartbeat.ahk
- C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\settings\imported\patternHashes.ahk
- C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\settings\imported\patterns.ahk
- C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\settings\nm_config.ini
- C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\settings\field_config.ini
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 410417c28d1d02787782…c79f95Never scannednever seen before
- 5640c958751ffbb3d697…f6a328Never scannednever seen before
- 603f75f7d6c46ed19e57…1a5988Never scannednever seen before
- 113cd775a600efc90a26…7e1219Never scannednever seen before
- e0750f67c6646439a026…cacb88Never scannednever seen before
- 0c9bfe048c95dec41be0…09c2b8Never scannednever seen before
- 0039163583c7c6d9ff3a…6b6cb5Never scannednever seen before
- 1fd44d3b393a5d1ecb18…a3ab3aNever scannednever seen before
- 801ee8311a040e1f8f55…5e03ebNever scannednever seen before
- 5a4f51b7efd7f1982780…0d60acNever scannednever seen before
Servers this file contacts
This file contacts 1 host we've flagged suspicious in our own URL scanner.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 4 / 74engines flagged
- 89sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
4 of 74 antivirus engines flagged the file, including Fortinet and VBA32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 111 times from 89 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: NatroMacro-fix(1).zip — 5434b6ace7df73b6c025f7e2c59523f0813bb9c79e1e61c51360e3cce5e51dfd
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset/nm_image_assets/Styles/USkin.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset/START.bat^"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Heartbeat.ahk — C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\submacros\Heartbeat.ahk
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: patternHashes.ahk — C:\Users\<USER>\AppData\Local\Temp\NatroMacroDev-new-reset\settings\imported\patternHashes.ahk
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: raw.githubusercontent.com — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 09
Contacted host: 140.82.114.5 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence140.82.114.5 · 185.199.109.133 · 23.195.81.176
4 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- NatroMacro-fix(1).zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 7.3 MB
- Last analyzed
- Sep 19, 2026, 12:56 PM UTC
5434b6ace7df73b6c025f7e2c59523f0813bb9c79e1e61c51360e3cce5e51dfdSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or extract it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is NatroMacro-fix(1).zip safe, or is it malware?
What is NatroMacro-fix(1).zip?
How many antivirus engines detected NatroMacro-fix(1).zip?
What should I do if I already opened or extracted NatroMacro-fix(1).zip?
How do I remove NatroMacro-fix(1).zip?
What kind of malware is NatroMacro-fix(1).zip?
What is the SHA-256 hash of NatroMacro-fix(1).zip?
How up to date is this analysis of NatroMacro-fix(1).zip?
Community
Member reviews and reports for this exact file hash.