Is slayers-2-fishing-windows.zip safe?
No antivirus engine detected malware, but one sandbox mapped several offensive techniques, including possible process injection and defense impairment, warranting caution.
All 75 antivirus engines were free of detections, and the only observed host was fully checked without a reputation hit. However, one sandbox mapped possible process injection, data destruction, PowerShell, and defense impairment, while the archive and its ten unresolved children are very new.
0f71d4514ad4823445…8a034c3dbfe7eeRecommended 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, and the only observed host was fully checked without a reputation hit. However, one sandbox mapped possible process injection, data destruction, PowerShell, and defense impairment, while the archive and its ten unresolved children are very new.
The antivirus results are strongly reassuring: none of 75 engines raised a detection, including all 17 participating tier-1 engines. One completed sandbox run nevertheless mapped four offensive techniques, including possible process injection and defense impairment, so the runtime evidence cannot be dismissed. That sandbox did not issue a malicious conclusion, and the sole observed domain was fully covered by the host check without a reputation hit. None of the ten inspected child files was identified as malware, but all remain unresolved rather than established as benign. The file is newly observed yet already has 201 distinct submitters, which reduces rarity concerns while leaving the unusual behavior unexplained.
What We Detected
No detections were reported by 75 antivirus engines, including 17 tier-1 engines. Researcher intelligence also returned no CIRCL, MalwareBazaar, or YARAify match. The archive is only one day old but has appeared from 201 distinct sources across 227 submissions.
Threat Behavior
One completed sandbox run mapped T1055 process injection, T1059.001 PowerShell, T1485 data destruction, and T1562.001 defense impairment. These mappings are concerning, but the sandbox did not issue a malicious conclusion, and the process-injection heuristic explicitly notes that it does not establish the exact method or intent. The sole observed domain, assets.msn.com, was covered by the host-reputation check and produced no malicious or suspicious hit. Ten child files were inspected without a malware finding, although their individual verdicts remain unresolved.
What To Do Now
Keep endpoint protection enabled and avoid running the included batch files on an important system until the archive's source and intended function are verified. If testing is necessary, use an isolated disposable environment and review the scripts before execution.
Where this verdict could be wrong3 caveats
- The saved runtime mapping includes T1055 process injection, T1485 data destruction, and T1562.001 defense impairment; these are serious behavioral indicators even though no sandbox issued a malicious verdict.
- The archive is only one day old, and all 10 inspected dropped children have unknown verdicts, so child-file assurance remains incomplete.
- file.tags includes detect-debug-environment and long-sleeps, which can indicate sandbox evasion but are not independently conclusive.
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 of 75 antivirus engines reported a detection.
- All 17 participating tier-1 engines reported no detection.
- The completed sandbox did not issue a malicious verdict.
- The sole observed host was fully checked without a malicious or suspicious reputation hit.
- No CIRCL, MalwareBazaar, or YARAify corroboration was present.
- Runtime evidence mapped T1055 process injection.
- Runtime evidence mapped T1485 data destruction and T1562.001 defense impairment.
- Tags indicate debugger detection and long sleeps, both compatible with sandbox evasion.
- The archive was first observed only one day ago.
- All 10 inspected child files remain individually unresolved.
Do not execute the batch files on a production device until their source and contents are verified. Keep security protection enabled and use an isolated disposable 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 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Complete1 contacted host was cross-checked.
YARA
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
- 13MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 16filesystem & 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.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Scans through your files and folders.
Moderate concern: Decoded or unpacked concealed content while running.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
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
slayers-2-fishing-windows.zip
0f71d4514ad48234458bdeede74455c9f657e028e23298fbf28a034c3dbfe7ee
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-26-07-52-31.334.log
C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-26-07-52-31.334.log
04Isolated runtime analysis - Written fileObserved
VRegDriver
\Device\VRegDriver
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
assets.msn.com
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.
- assets.msn.com
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-26-07-52-31.334.log
- \Device\VRegDriver
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-26-07-52-28.268.log
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-26-07-52-33.489.log
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- Global\OneSettingQueryMutex+compat+encapsulation
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
- ab531fc6c2216d7d6390…0e1afbNever scannednever seen before
- 392b8c42cc0e268a2b09…865ddbNever scannednever seen before
- 0c00a5b5ff4c9c7b56a6…9bbfc3Never scannednever seen before
- c508060dc3607a2a37df…01dd09Never scannednever seen before
- 75146db16b3b3fea1957…6d1bf6Never scannednever seen before
- 97fa07976eb48a5f37ed…a87145Never scannednever seen before
- be4f5b57965461308d9b…ec50e7Never scannednever seen before
- 42e7016927b92fbfbbc2…8f063eNever scannednever seen before
- ed7b00d529bdab5cd6e6…50f8a1Never 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 / 75engines flagged
- 201sources 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 227 times from 201 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: slayers-2-fishing-windows.zip — 0f71d4514ad48234458bdeede74455c9f657e028e23298fbf28a034c3dbfe7ee
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-26-07-52-31.334.log — C:\Users\<USER>\AppData\Local\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir\AppInstaller-2026-09-26-07-52-31.334.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: VRegDriver — \Device\VRegDriver
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: assets.msn.com — 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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -p
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
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
- slayers-2-fishing-windows.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 68.7 KB
- Last analyzed
- Sep 27, 2026, 10:09 AM UTC
0f71d4514ad48234458bdeede74455c9f657e028e23298fbf28a034c3dbfe7eeSafety & 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 slayers-2-fishing-windows.zip safe, or is it malware?
What is slayers-2-fishing-windows.zip?
How many antivirus engines detected slayers-2-fishing-windows.zip?
I already downloaded and opened or extracted slayers-2-fishing-windows.zip — what should I do?
How do I remove slayers-2-fishing-windows.zip?
What is the SHA-256 hash of 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.