Is Fallout 4 Engine Extender safe?
Unsigned Fallout 4 mod DLL shows process-injection behavior yet zero AV detections.
Seventy-five engines report the file clean, but the sandbox captured T1055 process injection and direct-IP traffic. Medium prevalence and unsigned status leave the intent ambiguous.
5d4058926ae8bd4414…1c52577e8d88c7Recommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened 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.
Seventy-five engines report the file clean, but the sandbox captured T1055 process injection and direct-IP traffic. Medium prevalence and unsigned status leave the intent ambiguous.
Zero engine detections across 75 scanners and no tier-1 consensus indicate the file is not widely recognized malware. However, the sandbox recorded MITRE T1055 and T1562.001 techniques plus direct-IP contact, and the DLL is unsigned. Medium prevalence with no prior similar-hash verdicts prevents a confident clean classification.
What We Detected
Seventy-five antivirus engines returned zero malicious flags. The file is an unsigned 64-bit DLL named "Fallout 4 Engine Extender" first seen two days ago. Sandbox execution logged process-injection activity (T1055) and evasion (T1562.001) plus a single direct-IP connection to 162.159.36.2.
Threat Behavior
Process injection and debug detection are common in game modding tools, yet they also appear in malware. No dropped children, persistence mechanisms, or known-malicious hosts were observed. Host-reputation cross-check coverage is incomplete.
What To Do Now
Run the DLL only inside an isolated Fallout 4 environment or test VM. Keep Windows Defender and other endpoint protection enabled. Monitor for unusual rundll32 activity or additional network connections.
Where this verdict could be wrong1 caveat
- Sandbox observed T1055 process injection and direct-IP contact, but no malicious sandbox verdict or known-bad host correlation.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines
- Medium prevalence with 18 submitters
- No dropped children or persistence
- Unsigned DLL
- Process-injection techniques observed
- Direct-IP contact without domain
Treat as untrusted until the mod author provides a code-signed build or independent verification from the Fallout 4 modding community.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete2 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
- 19MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 25filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
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: Scans through your files and folders.
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
Fallout 4 Engine Extender
5d4058926ae8bd44140ffd814e0bcd5be16d0b0799f7d7420a1c52577e8d88c7
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\f4ee.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 4544 -s 564
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
b7d2ec16-5314-4800-acab-8de86f560dd7
C:\ProgramData\Microsoft\Windows\WER\Temp\b7d2ec16-5314-4800-acab-8de86f560dd7
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\b7d2ec16-5314-4800-acab-8de86f560dd7
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\2bdaced5-f827-49b3-824c-7c27a81d7dfd
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6892
- \Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex3624
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6876
- \Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex4956
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7036
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
- 0 / 75engines flagged
- 18sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 18 times from 18 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Fallout 4 Engine Extender — 5d4058926ae8bd44140ffd814e0bcd5be16d0b0799f7d7420a1c52577e8d88c7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\f4ee.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 4544 -s 564
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: b7d2ec16-5314-4800-acab-8de86f560dd7 — C:\ProgramData\Microsoft\Windows\WER\Temp\b7d2ec16-5314-4800-acab-8de86f560dd7
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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.
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:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\f4ee.dll",#1The 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.
Evidence162.159.36.2
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Fallout 4 Engine Extender
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 1.1 MB
- Last analyzed
- Aug 27, 2026, 11:18 PM UTC
5d4058926ae8bd44140ffd814e0bcd5be16d0b0799f7d7420a1c52577e8d88c7Safety & 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 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 file 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 Fallout 4 Engine Extender safe, or is it malware?
What is Fallout 4 Engine Extender?
How many antivirus engines detected Fallout 4 Engine Extender?
I already downloaded and opened Fallout 4 Engine Extender — what should I do?
How do I remove Fallout 4 Engine Extender?
What is the SHA-256 hash of Fallout 4 Engine Extender?
How up to date is this analysis of Fallout 4 Engine Extender?
Community
Member reviews and reports for this exact file hash.