Is Extreme Injector.exe safe?
Unsigned PE with 11 tier-1 detections naming Extreme Injector hacktool and runtime evidence mapped to T1055 process-injection behavior.
53 of 75 engines flag the file, 11 of them tier-1, converging on the Extreme Injector hacktool family. Sandbox evidence shows T1055 process injection, debugger evasion, and direct-IP network calls to a suspicious host.
b65f40618f584303ca…a8facbe8195a46Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
53 of 75 engines flag the file, 11 of them tier-1, converging on the Extreme Injector hacktool family. Sandbox evidence shows T1055 process injection, debugger evasion, and direct-IP network calls to a suspicious host.
The combination of tier-1 consensus, explicit hacktool labels, and offensive MITRE techniques outweighs the file's age and moderate prevalence. Unsigned status and high-entropy code sections further support the malicious classification. Similar imphash matches have previously been labelled suspicious or malicious. No credible counter-evidence exists to downgrade the verdict.
What We Detected
11 tier-1 engines and 42 additional engines label the sample as the Extreme Injector hacktool. Microsoft specifically tags it 'HackTool:Win32/ExtremeInjector!pz'. YARAify reports 12 matching rules covering packing, debugger evasion, and obfuscation.
Threat Behavior
Runtime traces map to MITRE T1055 (process injection), T1543.003 (service creation), and T1562.001 (impair defenses). The binary contacts raw.githubusercontent.com (flagged suspicious) and 18 raw IP addresses. Ten dropped children were inspected; none carried independent malicious verdicts.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and remove the sample from disk. If found in an enterprise environment, scan surrounding systems for related injector components and review logs for unauthorized process injection attempts.
Where this verdict could be wrong1 caveat
- prevalence.classification=common_old (3654 submitters) — long-standing public tooling may attract mixed use.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 11 tier-1 malicious detections
- hacktoolConfirmed flag active
- T1055 process injection observed
- unsigned and high-entropy code
- suspicious contacted host in cache
Block and quarantine the file; treat any copies or related processes as malicious.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete53 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete9 signature or behavior rules 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
- 22MITRE ATT&CK techniques
- 15spawned processes
- 22network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
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.
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.exe
b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
settings.xml
C:\Users\<USER>\Desktop\settings.xml
04Isolated runtime analysis - Written fileObserved
settings.xml
C:\analyse\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.111.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.
- 185.199.111.133
- a83f:8110:6cf9:f3f8:db7a:68a6:13ee:648
- 192.168.0.107
- 185.199.109.133
- 185.199.110.133
- a83f:8110:cce1:d301:2000:0:0:0
- 13.107.4.50
- 192.168.0.2
- 185.199.108.133
- a83f:8110:0:0:1b00:100:2800:0
- https://raw.githubusercontent.com:443/master131/ExtremeInjector/master/version
- https://raw.githubusercontent.com/master131/ExtremeInjector/master/version
- C:\Users\<USER>\Desktop\settings.xml
- C:\analyse\settings.xml
- c:\analyse\settings.xml
- C:\Documents and Settings\Administrator\Local Settings\Temp\EB93A6\settings.xml
- C:\Users\<USER>\Downloads\settings.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3D3.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER8B5.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER952.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5E76.tmp.WERInternalMetadata.xml
- RasPbFile
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 20d42a8cf8e30141a32e…6019fdNever scannednever seen before
- 3eb8d392a0e31b0a6dcc…b0a5b8Never scannednever seen before
- 756c380f2014c7a338a6…f76f65Never scannednever seen before
- f9631aebd7f145b6dec6…5087d0Never scannednever seen before
- 458320d240f96b27e8c7…763248Never scannednever seen before
- 059db9d66f0011eb9c23…f6df4fNever scannednever seen before
- 2d7154bbc59a8091b3f8…272a0bNever scannednever seen before
- 1fa548561a2538b517c4…f8abb5Never scannednever seen before
- 4097542f33034dbd5945…81d009Never scannednever seen before
- 158c83d9c9def4722e63…aba8e4Never 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.
- 9rule hits recorded
- 53 / 75engines flagged
- 3,654sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
7 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
53 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,654 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: Extreme Injector.exe — b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: settings.xml — C:\Users\<USER>\Desktop\settings.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.xml — C:\analyse\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.111.133 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- BAZT_B5_NOCEXInvalidStream
- DebuggerCheck__QueryInfo
- DebuggerHiding__Thread
- INDICATOR_EXE_Packed_Dotfuscator
- INDICATOR_EXE_Packed_Goliath
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\<USER>\Desktop\software.exe"PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code sectionThe 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.
Evidence185.199.111.133 · a83f:8110:6cf9:f3f8:db7a:68a6:13ee:648 · 185.199.109.133Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidencehttps://raw.githubusercontent.com:443/master131/ExtremeInjector/master/version
53 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
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.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 1.9 MB
- Last analyzed
- Aug 18, 2026, 12:01 AM UTC
b65f40618f584303ca0bcf9b5f88c233cc4237699c0c4bf40ba8facbe8195a46Safety & 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 run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran 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
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Extreme Injector.exe malware?
What is Extreme Injector.exe?
How many antivirus engines detected Extreme Injector.exe?
I already downloaded and ran Extreme Injector.exe — what should I do?
How do I remove Extreme Injector.exe?
What kind of malware is Extreme Injector.exe?
What is the SHA-256 hash of Extreme Injector.exe?
How up to date is this analysis of Extreme Injector.exe?
Community
Member reviews and reports for this exact file hash.