Is PoeEnhancer-deps.zip safe?
No antivirus engine detected the archive, but process-injection and defense-evasion mappings plus an unchecked direct-IP contact justify caution before execution.
All 75 antivirus engines were free of detections, including the reporting tier-1 products, and no malicious dropped child or external intelligence match was established. However, one sandbox run mapped activity to process injection and defense evasion, while its direct-IP contact received no complete reputation check, so execution should be deferred pending verification.
9c4f217ef11e049403…f6de7d20f9fd6aRecommended 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 75 antivirus engines were free of detections, including the reporting tier-1 products, and no malicious dropped child or external intelligence match was established. However, one sandbox run mapped activity to process injection and defense evasion, while its direct-IP contact received no complete reputation check, so execution should be deferred pending verification.
The static scan produced no malicious or suspicious detections among 75 engines, and 16 tier-1 engines reported no detection. One completed sandbox run did not issue a malicious conclusion, but it mapped activity to T1055 and T1562.001. Those mappings appear alongside rundll32 loading libraries from a temporary path, making them relevant even though they do not establish hostile intent by themselves. The observed no complete contacted-host reputation result was available because no complete host-reputation result is available. No malicious child, known-sample match, or researcher-rule match corroborates malware, so the evidence remains mixed rather than conclusive.
What We Detected
The archive received 0 detections from 75 antivirus engines, with tier1Malicious=0 and 16 tier-1 products reporting no detection. External checks also produced no known-sample or researcher-rule matches: YARAify returned zero rules, CIRCL returned no hit, and MalwareBazaar returned no hit.
Threat Behavior
One sandbox run mapped activity to T1055 (Process Injection) and T1562.001 (Impair Defenses). The recorded execution included rundll32 loading several DLLs from a temporary directory. It also contacted 162.159.36.2 directly, but contactedHosts=null means no complete reputation result is available for that address. Five dropped children were inspected without an identified malicious child, although four lack stored verdicts.
What To Do Now
Do not run the archive on a production system until its source and expected contents are verified. Keep endpoint protection enabled, inspect the extracted executables and DLLs individually, and use an isolated environment if further testing is necessary.
Where this verdict could be wrong3 caveats
- The runtime mapping includes T1055 process injection and T1562.001 impairment of defenses, which are offensive techniques and warrant caution despite zero antivirus detections.
- The direct-IP connection to 162.159.36.2 was not reputation-checked because contactedHosts=null.
- Four of five inspected dropped children have no stored verdict, limiting confidence in the child-file assessment.
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/75 antivirus engines reported a detection
- 16 tier-1 engines reported no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false
- No CIRCL, MalwareBazaar, or YARAify match
- Runtime mapping to T1055 process injection
- Runtime mapping to T1562.001 impairment of defenses
- rundll32 loaded DLLs from a temporary directory
- Direct-IP contact to 162.159.36.2 lacks a completed reputation check
- Four dropped children have no stored verdict
Verify the archive against the developer's official release channel and scan each extracted component before use. Keep endpoint protection enabled and test only in an isolated environment if provenance cannot be confirmed.
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
- 8MITRE ATT&CK techniques
- 9spawned processes
- 1network contacts
- 31filesystem & 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
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: Reads your Windows user-account details.
Note: Listed running processes; both legitimate software and malware may do this.
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
PoeEnhancer-deps.zip
9c4f217ef11e049403b2985204ecbf3cce8abaf882d4cf4f98f6de7d20f9fd6a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\oo2core_9_win64.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\WerFault.exe -u -p 3132 -s 588
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
cdf193ea-9c97-4c27-9d79-faf5c1f793bd
C:\ProgramData\Microsoft\Windows\WER\Temp\cdf193ea-9c97-4c27-9d79-faf5c1f793bd
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\cdf193ea-9c97-4c27-9d79-faf5c1f793bd
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\b79b6b4f-4b11-4a94-a69f-541fb7b41f02
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFD3.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD717.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD9D7.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERCFD3.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERD717.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess3132
- Global\29dca3e9-3bf0-44e0-ab24-421d8933cd2a
- Local\WERReportingForProcess3140
- Global\a189bdd7-b295-4c63-af14-4f7f0d03a174
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- 145ade963eba427027d5…da246fNever scannednever seen before
- 647688159aa6af0baa8a…cf5427Never scannednever seen before
- a0b0c4ad73abc572a953…8660d6Never scannednever seen before
- 9b203e40323b49dad295…a847d4Clean0/75 enginestrust 88from our cache
- 9f3027381f3c40b63e55…df519cNever 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 / 75engines flagged
- 1sources 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 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: PoeEnhancer-deps.zip — 9c4f217ef11e049403b2985204ecbf3cce8abaf882d4cf4f98f6de7d20f9fd6a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\oo2core_9_win64.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\WerFault.exe -u -p 3132 -s 588
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: cdf193ea-9c97-4c27-9d79-faf5c1f793bd — C:\ProgramData\Microsoft\Windows\WER\Temp\cdf193ea-9c97-4c27-9d79-faf5c1f793bd
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\oo2core_9_win64.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
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
- PoeEnhancer-deps.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 7.7 MB
- Last analyzed
- Sep 17, 2026, 8:33 PM UTC
9c4f217ef11e049403b2985204ecbf3cce8abaf882d4cf4f98f6de7d20f9fd6aSafety & 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 PoeEnhancer-deps.zip safe, or is it malware?
What is PoeEnhancer-deps.zip?
How many antivirus engines detected PoeEnhancer-deps.zip?
What should I do if I already opened or extracted PoeEnhancer-deps.zip?
How do I remove PoeEnhancer-deps.zip?
What is the SHA-256 hash of PoeEnhancer-deps.zip?
How up to date is this analysis of PoeEnhancer-deps.zip?
Community
Member reviews and reports for this exact file hash.