Is Loader - INJ4ALL (3).rar safe?
Only MaxSecure flagged the archive, but DLL execution, defense-evasion telemetry, and incomplete network and child-file verdicts warrant caution before opening it.
The antivirus result strongly resembles a false positive: only 1 of 76 engines detected it, and that detection came from a low-trust engine. However, one sandbox run showed DLL execution through rundll32.exe and T1562.001, while network reputation and all nine extracted-child verdicts remain unresolved.
2b67775b8f4d8f8996…3d5f89c990de82Recommended 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 antivirus result strongly resembles a false positive: only 1 of 76 engines detected it, and that detection came from a low-trust engine. However, one sandbox run showed DLL execution through rundll32.exe and T1562.001, while network reputation and all nine extracted-child verdicts remain unresolved.
MaxSecure was the only detector among 76 engines, while all 17 reporting tier-1 engines were silent, making the generic Trojan label weak. One completed sandbox run nevertheless showed the archive's DLL being launched through rundll32.exe and recorded T1562.001. The credential-dumper heuristic is not conclusive because its evidence only lists lsass.exe as a process and does not demonstrate memory access. Numerous IP contacts were recorded, but no complete host-reputation result is available. Nine extracted children produced no confirmed malicious child, although each remains unclassified, leaving meaningful uncertainty.
What We Detected
Only MaxSecure flagged the archive, reporting a generic Trojan label; the other 75 engines did not flag it, including all 17 reporting tier-1 engines. This low-trust-only detection pattern has a high likelihood of being a false positive.
Threat Behavior
One sandbox run launched LoaderINJ4ALL.dll through rundll32.exe and recorded T1562.001, which can be associated with impairing defenses. A credential-dumper heuristic also fired, but its supplied evidence only shows lsass.exe in the process list rather than a demonstrated LSASS memory read. The sample contacted multiple IP addresses, yet no complete host-reputation result is available. Nine child files were inspected without a confirmed malicious result, but all nine remain unclassified.
What To Do Now
Do not open or extract this archive on a production system unless its source and purpose are independently verified. Keep endpoint protection enabled and, if analysis is necessary, use an isolated disposable environment while separately scanning the extracted files.
Where this verdict could be wrong3 caveats
- The T1562.001 runtime signal and rundll32.exe DLL execution can indicate defense evasion or proxy execution.
- MalwareTips.Synth.DirectIpC2 fired because the run contacted numerous IP addresses without recorded domains, but contactedHosts=null prevents reputation corroboration.
- Nine dropped children have unknown verdicts; hasMaliciousChild=false therefore does not establish that the extracted contents are 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 1/76 engines detected the archive.
- engines.tier1Malicious=0 and engines.onlyLowTrustFlagging=true.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- externalIntel.circl.hit=false.
- Sandbox recorded T1562.001, a defense-evasion technique.
- A DLL was launched through rundll32.exe.
- Direct-IP network activity lacks a complete host-reputation cross-check.
- All nine extracted child files remain unclassified.
- The archive name suggests loader or injection functionality.
Avoid opening the archive until its origin and extracted contents are verified. Keep security protection enabled and use an isolated disposable environment if inspection is required.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 6MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 17filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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: 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
Loader - INJ4ALL (3).rar
2b67775b8f4d8f8996c73d6292e4570e5bf3e82d985cbb6dc43d5f89c990de82
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Loader - INJ4ALL/LoaderINJ4ALL.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\Loader - INJ4ALL/LoaderINJ4ALL.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984
\Device\NamedPipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984
04Isolated runtime analysis - Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
23.45.189.145
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
13.107.226.70
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.
- 23.45.189.145
- 13.107.226.70
- 13.107.6.158
- 13.107.253.70
- 23.67.33.89
- 20.9.155.145
- 4.153.187.221
- 13.107.226.69
- 150.171.28.10
- 52.184.215.111
- \Device\NamedPipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_1784_1637634694\BIT2C75.tmp
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_1784_1637634694\9d2b0a50-e1ed-42cf-8889-eb3d61bf9dde
- C:\Users\<USER>\AppData\Local\Temp\edge_BITS_1784_1809468181\BIT6E61.tmp
- C:\ProgramData\Microsoft\Windows\LfSvc\Cache
- \Sessions\1\BaseNamedObjects\DBWinMutex
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- ef6742d8d7dc2c9733ed…961055Never scannednever seen before
- 36223094774a1bf4f828…080d93Never scannednever seen before
- 9d6ac22121d05a7eb0ae…ca1c85Never scannednever seen before
- aad8773da12f4fc2a824…a3697aNever scannednever seen before
- ff5b91ed49e6d7d633d0…4a4b00Never scannednever seen before
- 57e7c16e7226c9a29dbc…e7b714Never scannednever seen before
- 6012062d86e551bd506a…8e0f20Never scannednever seen before
- fa29a6d5775ff340900a…9c61a0Never scannednever seen before
- ae603ef619c54b32f683…9ed19fNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 1 / 76engines flagged
- 15sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 76 antivirus engines flagged the file, including MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 18 times from 15 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Loader - INJ4ALL (3).rar — 2b67775b8f4d8f8996c73d6292e4570e5bf3e82d985cbb6dc43d5f89c990de82
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\Loader - INJ4ALL/LoaderINJ4ALL.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\Loader - INJ4ALL/LoaderINJ4ALL.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984 — \Device\NamedPipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 23.45.189.145 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.226.70 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
Sandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence23.45.189.145 · 13.107.226.70 · 13.107.6.158
1 of 76 engines flagged this file
View all 76 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
- Loader - INJ4ALL (3).rar
- Format
- RAR
- Code signing
- Not applicable to this file type
- Size
- 77.8 KB
- Last analyzed
- Sep 17, 2026, 5:40 PM UTC
2b67775b8f4d8f8996c73d6292e4570e5bf3e82d985cbb6dc43d5f89c990de82Safety & 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 Loader - INJ4ALL (3).rar safe, or is it malware?
What is Loader - INJ4ALL (3).rar?
How many antivirus engines detected Loader - INJ4ALL (3).rar?
What should I do if I already opened or extracted Loader - INJ4ALL (3).rar?
How do I remove Loader - INJ4ALL (3).rar?
What is the SHA-256 hash of Loader - INJ4ALL (3).rar?
How up to date is this analysis of Loader - INJ4ALL (3).rar?
Community
Member reviews and reports for this exact file hash.