Is slayers-2-fishing-windows.zip safe?
No antivirus engine detected malware, while one sandbox recorded sensitive techniques that remain uncorroborated by a malicious runtime conclusion or external intelligence.
All 74 antivirus engines returned no malicious or suspicious detection, including 17 tier-1 engines. One sandbox mapped activity to process injection and defense impairment, but issued no malicious conclusion; because the archive is newly observed and its extracted children remain unclassified, normal caution is still appropriate.
78d6d0eff5a1f8712b…8ff7780f22325dRecommended next actions
Before opening or extracting
Open or extract it only when its sender or download source has been independently verified.
If you already opened or extracted it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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 returned no malicious or suspicious detection, including 17 tier-1 engines. One sandbox mapped activity to process injection and defense impairment, but issued no malicious conclusion; because the archive is newly observed and its extracted children remain unclassified, normal caution is still appropriate.
The strongest evidence is the complete absence of detections across 74 antivirus engines, including 17 tier-1 products. A completed sandbox run recorded T1055 and T1562.001, but did not issue a malicious conclusion, so those mappings are treated as cautionary rather than decisive. Ten extracted files were inspected without a confirmed malicious child, although each child remains unclassified. Research intelligence produced no CIRCL, MalwareBazaar, or YARAify match. The file is newly observed, and no complete contacted-host reputation check was saved, which limits confidence.
What We Detected
None of 74 antivirus engines flagged the ZIP as malicious or suspicious, and all 17 reporting tier-1 engines returned no detection. No matching family, YARAify rule, CIRCL record, or MalwareBazaar entry was found.
Threat Behavior
One completed sandbox run mapped activity to T1055 process injection and T1562.001 impairment of defenses. The sandbox did not issue a malicious conclusion, no persistence indicators were recorded, and no network contacts were observed during that run. However, no complete host-reputation cross-check was saved. Ten extracted files were inspected without a confirmed malicious child, but their individual verdicts remain unknown.
What To Do Now
Keep endpoint protection enabled and obtain the archive from its official source. Because the file is newly observed and contains batch scripts, inspect or execute it only in a controlled environment if its origin cannot be verified.
Where this verdict could be wrong3 caveats
- The sandbox mapped activity to T1055 process injection and T1562.001 impairment of defenses; these techniques warrant caution despite the absence of engine detections.
- All 10 dropped children have unknown verdicts, so hasMaliciousChild=false does not establish that every extracted component is benign.
- The archive was first submitted 0 days ago, limiting historical reputation and time for signature-based detections to develop.
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 detected a threat
- 17 tier-1 engines reported no detection
- No malicious sandbox conclusion
- No confirmed malicious dropped child
- No CIRCL, MalwareBazaar, or YARAify hit
- Sandbox mapping to T1055 process injection
- Sandbox mapping to T1562.001 impairment of defenses
- First observed 0 days ago
- All 10 extracted children remain unclassified
- No complete contacted-host reputation result is available
Keep endpoint protection enabled and use only a copy obtained from a trusted official source. If the source is uncertain, inspect the batch scripts or run the archive in an isolated environment.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule 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
- 15spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
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
slayers-2-fishing-windows.zip
78d6d0eff5a1f8712b6fe5dcde449c3aa5a171bf357665d8fd8ff7780f22325d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\slayers-2-fishing-windows/Launch.bat^"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\slayers-2-fishing-windows/Launch.bat
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
AppInstaller-2026-09-20-18-48-40.350.log
C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-40.350.log
04Isolated runtime analysis - Written fileObserved
AppInstaller-2026-09-20-18-48-33.096.log
C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-33.096.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-40.350.log
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-33.096.log
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-34.496.log
- \Device\VRegDriver
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fe5b5159307586c082ba…f8b524Never scannednever seen before
- fd56485e13aea77c90b9…9819c6Never scannednever seen before
- 392b8c42cc0e268a2b09…865ddbNever scannednever seen before
- d17c56e25ab7d75a7845…916513Never scannednever seen before
- 60fa14bc4321dd96c13c…fcbb99Never scannednever seen before
- 75146db16b3b3fea1957…6d1bf6Never scannednever seen before
- 97fa07976eb48a5f37ed…a87145Never scannednever seen before
- 42e7016927b92fbfbbc2…8f063eNever scannednever seen before
- e4b33b1dce41386b1a29…b7c2a4Never scannednever seen before
- e9640e4ad776bec187df…6ca1f9Never 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.
- 1rule hit recorded
- 0 / 74engines flagged
- 10sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 11 times from 10 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: slayers-2-fishing-windows.zip — 78d6d0eff5a1f8712b6fe5dcde449c3aa5a171bf357665d8fd8ff7780f22325d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\slayers-2-fishing-windows/Launch.bat^"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\slayers-2-fishing-windows/Launch.bat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AppInstaller-2026-09-20-18-48-40.350.log — C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-40.350.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: AppInstaller-2026-09-20-18-48-33.096.log — C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-20-18-48-33.096.log
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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -p
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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- slayers-2-fishing-windows.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 50.9 KB
- Last analyzed
- Sep 21, 2026, 12:42 AM UTC
78d6d0eff5a1f8712b6fe5dcde449c3aa5a171bf357665d8fd8ff7780f22325dSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or extract it only when its sender or download source has been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is slayers-2-fishing-windows.zip safe?
What is slayers-2-fishing-windows.zip?
How many antivirus engines detected slayers-2-fishing-windows.zip?
What is the SHA-256 hash of slayers-2-fishing-windows.zip?
Is it safe to open or extract slayers-2-fishing-windows.zip?
How up to date is this analysis of slayers-2-fishing-windows.zip?
Community
Member reviews and reports for this exact file hash.