Is Extreme.Injector.v3.7.3.-.by.master131.rar safe?
Multiple tier-1 engines confirm injection and hacktool functionality, while the archive extracts a child detected by 53 of 75 antivirus engines.
This archive contains a confirmed DLL-injection tool, with 49 of 75 engines flagging it and 11 tier-1 engines contributing independent detections. One extracted child was also detected by 53 of 75 engines, so the file should not be opened or executed.
93dda8b91586acf53c…ad67190361bce8Recommended next actions
Before opening or extracting
Do not open or extract it. Delete this archive from the device, then empty the Recycle Bin or Trash.
If you already opened or extracted it
Close it. If it opened links, requested credentials, or triggered unexpected behavior, disconnect from the internet and run a full device scan.
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.
This archive contains a confirmed DLL-injection tool, with 49 of 75 engines flagging it and 11 tier-1 engines contributing independent detections. One extracted child was also detected by 53 of 75 engines, so the file should not be opened or executed.
The strongest evidence is engines.hacktoolConfirmed=true, supported by tier-1 products including BitDefender, Emsisoft, GData, and Ikarus. Overall, 49 of 75 engines flagged the archive, with 11 independent tier-1 malicious votes and repeated DLL-injector or hacktool labels. Runtime analysis observed T1562.001, while one of eight inspected extracted files was detected by 53 of 75 engines. The single sandbox verdict was clean, but one run cannot outweigh the confirmed offensive functionality and malicious child. Host-reputation coverage was incomplete because only the domain was cross-checked while three IPs and a URL were also observed. Community comments were disregarded because adversarialInputFlags.commentInjectionSuspected=true.
What We Detected
The RAR archive was flagged by 49 of 75 antivirus engines, including 11 independent tier-1 detections. BitDefender, Emsisoft, GData, and Ikarus identify hacktool functionality, while ESET-NOD32 and Fortinet identify the DllInject family. The corroborated injector labels satisfy engines.hacktoolConfirmed=true.
Threat Behavior
The archive extracted executable content, and one of eight inspected children was detected by 53 of 75 engines. Runtime analysis also recorded T1562.001, a technique associated with impairing defenses. The sample contacted raw.githubusercontent.com, which was marked suspicious, but complete reputation coverage was unavailable for all observed IPs and the full no complete contacted-host reputation result was available result, that isolated result conflicts with the confirmed offensive capability and detected child.
What To Do Now
Do not extract or run this archive. Quarantine or remove it while keeping antivirus and endpoint protection enabled. If it was already executed, run a full system scan and review the host for injected processes or other unexpected activity.
Where this verdict could be wrong3 caveats
- behaviour.sandboxVerdicts contains one clean result, but that conflicts with the confirmed injector classification and malicious dropped child.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage limitations rather than exoneration.
- The archive is common and long-established, with prevalence.uniqueSources=3728 and prevalence.timesSubmitted=19573, but prevalence does not neutralize confirmed offensive tooling.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The single completed sandbox run returned a clean verdict.
- No persistence indicators were recorded in behaviour.persistenceIndicators.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false.
- The file has been widely submitted since 2017.
- 49 of 75 antivirus engines reported a malicious result.
- 11 independent tier-1 engines detected the archive.
- engines.hacktoolConfirmed=true for DLL-injection functionality.
- One extracted child was detected by 53 of 75 engines.
- Runtime analysis recorded MITRE technique T1562.001.
- raw.githubusercontent.com was marked suspicious by the host cache.
Quarantine or delete the archive and do not extract its contents. If execution already occurred, keep protection enabled, perform a full scan, and investigate running processes for injection activity.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete49 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 4 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
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
- 15MITRE ATT&CK techniques
- 13spawned processes
- 5network contacts
- 11filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Drops additional malware files onto your PC when it runs.
High concern: Used an input-capture technique that can record credentials or keystrokes.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Communicates over the network in a non-standard way.
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.
Threat context
How hacktools are abused
This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.
Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.
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
Extreme.Injector.v3.7.3.-.by.master131.rar
93dda8b91586acf53c70dfd3f512fcff5793a9af69e174d7e3ad67190361bce8
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\Extreme Injector v3.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\SysWOW64\unarchiver.exe" "C:\Users\user\Desktop\Extreme Injector.rar"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Dropped fileDerived
b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46
Saved child-file verdict: malicious.
04Dropped-file analysis - Written fileObserved
settings.xml
C:\Users\<USER>\Desktop\settings.xml
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
185.199.109.133
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.
- raw.githubusercontent.com
- 185.199.109.133
- 185.199.108.133
- 185.199.111.133
- https://raw.githubusercontent.com:443/master131/ExtremeInjector/master/version
- \\REGISTRY\A\{83b1176c-fcd9-11eb-8629-167c9a143b14}\DefaultObjectStore\LruList\CurrentLru
- HKU\S-1-5-21-575823232-3065301323-1442773979-1000\Software\WinRAR\Interface\Themes\ShellExtIcon
- HKU\S-1-5-21-575823232-3065301323-1442773979-1000\Software\WinRAR\Interface\Themes\ShellExtBMP
- HKLM\Software\Microsoft\Tracing\Extreme Injector v3_RASAPI32\FileDirectory
- HKLM\Software\Microsoft\Tracing\Extreme Injector v3_RASAPI32\MaxFileSize
- HKLM\Software\Microsoft\Tracing\Extreme Injector v3_RASAPI32\ConsoleTracingMask
- C:\Users\<USER>\Desktop\settings.xml
- C:\Users\user\AppData\Local\Temp\0bpdmgqv.sao
- C:\Users\user\AppData\Local\Temp\0bpdmgqv.sao\Extreme Injector v3.exe
- C:\Users\user\AppData\Local\Temp\unarchiver.log
- C:\Users\user\AppData\Roaming
Files this sample writes at runtime
The sandbox saw this file drop 8 children. 1 of them is already known-malicious in our database — this file is a dropper.
- b65f40618f584303ca0b…195a46Malicious53/75 enginestrust 12from our cache
- 84aff16f44c53402c567…6ca3f5Never scannednever seen before
- 6469107785621d76885f…4da7aeNever scannednever seen before
- 02dbf5e7dce17997a531…2e1364Never scannednever seen before
- 2ed4da1dca42e08a3fc2…fcf892Never scannednever seen before
- 4ef948c5ad93ea1d97df…016f24Never scannednever seen before
- 180e6672a714a1594d28…dfe88eNever scannednever seen before
- 86d4911a264905e719eb…608945Never 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.
- 0rule hits recorded
- 49 / 75engines flagged
- 3,728sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The file created or unpacked 1 malicious payload.
Verdict inputView chapterProvenanceDerivedSourceDropped-file analysisObserved at - 02
49 of 75 antivirus engines flagged the file, including AhnLab-V3 and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,728 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: Extreme.Injector.v3.7.3.-.by.master131.rar — 93dda8b91586acf53c70dfd3f512fcff5793a9af69e174d7e3ad67190361bce8
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\Extreme Injector v3.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\SysWOW64\unarchiver.exe" "C:\Users\user\Desktop\Extreme Injector.rar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Dropped file: b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46 — Saved child-file verdict: malicious.
ProvenanceDerivedSourceDropped-file analysisObserved at - 08
File written: settings.xml — C:\Users\<USER>\Desktop\settings.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: raw.githubusercontent.com — Saved reputation verdict: suspicious.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: 185.199.109.133 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
49 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Extreme.Injector.v3.7.3.-.by.master131.rar
- Format
- RAR
- Code signing
- Not applicable to this file type
- Size
- 1.2 MB
- Last analyzed
- Sep 26, 2026, 2:54 AM UTC
93dda8b91586acf53c70dfd3f512fcff5793a9af69e174d7e3ad67190361bce8Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't open or extract this archive. Delete this archive from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already opened or extracted it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
It can drop extra files, so run a full system scan — not just a quick one — to catch anything it left behind.
- Recovery step 05
Get a fresh copy from the original trusted source and verify its exact hash when possible.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Extreme.Injector.v3.7.3.-.by.master131.rar a virus?
What is Extreme.Injector.v3.7.3.-.by.master131.rar?
How many antivirus engines detected Extreme.Injector.v3.7.3.-.by.master131.rar?
What should I do if I already opened or extracted Extreme.Injector.v3.7.3.-.by.master131.rar?
How do I remove Extreme.Injector.v3.7.3.-.by.master131.rar?
What kind of malware is Extreme.Injector.v3.7.3.-.by.master131.rar?
What is the SHA-256 hash of Extreme.Injector.v3.7.3.-.by.master131.rar?
How up to date is this analysis of Extreme.Injector.v3.7.3.-.by.master131.rar?
Community
Member reviews and reports for this exact file hash.