Is EA DLC Unlocker v2 160-0.zip safe?
No antivirus engine detected this archive, but process-injection, service, protection-impairment, and unresolved direct-IP activity warrant caution before execution.
All 74 antivirus engines avoided flagging the archive, including 17 tier-1 engines, and the sandbox did not issue a malware finding. However, execution involved DLL loading through rundll32 and techniques mapped to process injection, service creation, and protection impairment; the contacted IP was not reputation-checked.
83880888daf0881813…c0a80e4bc6e5a5Recommended 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.
All 74 antivirus engines avoided flagging the archive, including 17 tier-1 engines, and the sandbox did not issue a malware finding. However, execution involved DLL loading through rundll32 and techniques mapped to process injection, service creation, and protection impairment; the contacted IP was not reputation-checked.
Static scanning found no detections among 74 engines, including 17 tier-1 products. One completed sandbox run nevertheless mapped activity to T1055, T1543.002, and T1562.001, which are materially riskier than ordinary archive extraction. The recorded rundll32 loading of a DLL could fit the unlocker's patching purpose, but it also resembles a common execution technique used by malware. Direct-IP contact to 162.159.36.2 was observed, and no complete host-reputation result is available because the contacted-host check is missing. Ten extracted children produced no malware finding, but each child remains without a conclusive verdict, leaving mixed evidence rather than firm corroboration.
What We Detected
The archive received 0 detections from 74 antivirus engines, with all 17 tier-1 engines reporting no detection. No named malware family, corroborated hacktool label, YARA rule, or curated threat-intelligence hit was present.
Threat Behavior
One sandbox run observed rundll32 loading version.dll and mapped activity to T1055, T1543.002, and T1562.001. These mappings indicate possible process injection, service-related execution, and impairment of security controls, although the sandbox itself did not issue a malware finding. The sample also contacted 162.159.36.2 directly; because contactedHosts is unavailable, no complete reputation result exists for that connection. Ten extracted files were inspected without a malware finding, but all ten remain unclassified.
What To Do Now
Avoid running the archive on a primary or sensitive system until its source and extracted components can be independently verified. Keep endpoint protection enabled, and use an isolated test environment if examination is necessary.
Where this verdict could be wrong3 caveats
- The complete 0/74 engine result, including 17 tier-1 non-detections, weighs strongly against a known malware family.
- behaviour.hasMaliciousSandboxVerdict=false, and no persistence indicators, mutexes, or registry modifications were recorded.
- The sample had 419 unique submitters and 464 submissions, so it is not an isolated file despite being only 22 days old.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 antivirus engines reported a detection.
- tier1Malicious=0 and tier1ReportedClean=17.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, CIRCL, and MalwareBazaar returned no corroborating hit.
- Runtime evidence maps activity to T1055 process injection.
- Runtime evidence maps activity to T1543.002 service-related execution.
- Runtime evidence maps activity to T1562.001 impairment of security tools.
- rundll32.exe loaded an extracted version.dll by ordinal.
- Direct-IP traffic to 162.159.36.2 lacks a completed reputation check.
- All 10 inspected child files remain unclassified.
Do not execute it on a primary system without verifying the source and extracted DLLs. Keep security protection enabled and use an isolated environment if testing is required.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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
- 12MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 15filesystem & 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: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
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
EA DLC Unlocker v2 160-0.zip
83880888daf08818137ae4129da2166feecf237c27aea9064dc0a80e4bc6e5a5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\EA DLC Unlocker v2/ea_app/version.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\EA DLC Unlocker v2/origin/version.dll",#1
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
bivryte1.qu5
C:\Users\user\AppData\Local\Temp\bivryte1.qu5
04Isolated runtime analysis - Written fileObserved
EA DLC Unlocker v2
C:\Users\user\AppData\Local\Temp\bivryte1.qu5\EA DLC Unlocker v2
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:\Users\user\AppData\Local\Temp\bivryte1.qu5
- C:\Users\user\AppData\Local\Temp\bivryte1.qu5\EA DLC Unlocker v2
- C:\Users\user\AppData\Local\Temp\bivryte1.qu5\EA DLC Unlocker v2\config.ini
- C:\Users\user\AppData\Local\Temp\bivryte1.qu5\EA DLC Unlocker v2\ea_app
- C:\Users\user\AppData\Local\Temp\bivryte1.qu5\EA DLC Unlocker v2\ea_app\version.dll
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- e305b8a3399785fb4393…cdd990Never scannednever seen before
- cf784476719a93e3fb84…0d2b83Never scannednever seen before
- 87df6f4f1c246e0e5d43…215052Never scannednever seen before
- 070ac609263921f4c910…2c0b89Never scannednever seen before
- 10f6a2254d2526fe93e0…36ddedNever scannednever seen before
- cfbe14fc02f08a2b941d…8945faNever scannednever seen before
- 5fd6759c0fd98eff60c5…608cb7Never scannednever seen before
- 06c8f383e8383c4b1736…e84c02Never scannednever seen before
- b6b4797b1ce41e14b7c3…f1b1f6Never scannednever seen before
- f66f3e8899c43a8433af…3e60d6Never 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
- 0 / 74engines flagged
- 419sources 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 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 464 times from 419 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: EA DLC Unlocker v2 160-0.zip — 83880888daf08818137ae4129da2166feecf237c27aea9064dc0a80e4bc6e5a5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\EA DLC Unlocker v2/ea_app/version.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\EA DLC Unlocker v2/origin/version.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: bivryte1.qu5 — C:\Users\user\AppData\Local\Temp\bivryte1.qu5
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: EA DLC Unlocker v2 — C:\Users\user\AppData\Local\Temp\bivryte1.qu5\EA DLC Unlocker v2
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\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\EA DLC Unlocker v2/ea_app/version.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 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- EA DLC Unlocker v2 160-0.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 1.2 MB
- Last analyzed
- Sep 20, 2026, 4:27 PM UTC
83880888daf08818137ae4129da2166feecf237c27aea9064dc0a80e4bc6e5a5Safety & 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 EA DLC Unlocker v2 160-0.zip safe, or is it malware?
What is EA DLC Unlocker v2 160-0.zip?
How many antivirus engines detected EA DLC Unlocker v2 160-0.zip?
I already downloaded and opened or extracted EA DLC Unlocker v2 160-0.zip — what should I do?
How do I remove EA DLC Unlocker v2 160-0.zip?
What is the SHA-256 hash of EA DLC Unlocker v2 160-0.zip?
How up to date is this analysis of EA DLC Unlocker v2 160-0.zip?
Community
Member reviews and reports for this exact file hash.