Is sniffcraft-windows-1.21.11 (1).exe safe?
Unsigned executable with one tier-1 detection and direct-IP contact but no sandbox or family consensus.
One tier-1 engine flagged the file as Trojan:Win32/Wacatac.B!ml while 70 others did not. The sample is unsigned, recently submitted, and contacted an IP address without domain context or host-reputation data.
df2bb8c1603ec386f7…386c7eed9f9096Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
One tier-1 engine flagged the file as Trojan:Win32/Wacatac.B!ml while 70 others did not. The sample is unsigned, recently submitted, and contacted an IP address without domain context or host-reputation data.
The single Microsoft detection lacks corroboration from other tier-1 engines or sandbox verdicts. Absence of signing and the direct-IP heuristic add uncertainty, yet no malicious child files, no external-intel hits, and medium prevalence prevent a malicious call. The combination of signals places the file in mixed-signals territory.
What We Detected
75 engines scanned the 6 MB Win32 executable; only Microsoft reported a detection (Trojan:Win32/Wacatac.B!ml). No other tier-1 or tier-2 engines agreed. The file is unsigned and was first seen one day ago.
Threat Behavior
One sandbox execution recorded six ambient MITRE techniques and a single outbound connection to IP 162.159.36.2 with no domain name. No malicious dropped children or persistence mechanisms were observed. External-intel sources returned no matches.
What To Do Now
Do not run the file on production systems. Keep endpoint protection enabled and consider submitting the sample to additional analysis services for further context.
Where this verdict could be wrong1 caveat
- Single tier-1 detection (Microsoft) on a 1-day-old file with medium prevalence and no corroborating tier-1 or sandbox signals
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 70/75 engines undetected
- No malicious dropped children
- No external-intel hits
- Unsigned executable
- Single tier-1 detection
- Direct-IP contact without domain
Treat the file as untrusted; avoid execution until additional reputable sources confirm its safety.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
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
- 6MITRE ATT&CK techniques
- 3spawned processes
- 1network contacts
- 4filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 1 server during sandbox analysis.
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
sniffcraft-windows-1.21.11 (1).exe
df2bb8c1603ec386f71ef74bd68dd0d38cc4cd56c2e59b438a386c7eed9f9096
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\sniffcraft-windows-1.21.11.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\sniffcraft-windows-1.21.11.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
conf.json
C:\Users\<USER>\Desktop\conf.json
04Isolated runtime analysis - Written fileObserved
conf.json
C:\Users\user\Desktop\conf.json
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>\Desktop\conf.json
- C:\Users\user\Desktop\conf.json
- \Device\ConDrv
- \Device\ConDrv\\Connect
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 74234e98afe7498fb5da…82b90bNever 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
- 1 / 75engines flagged
- 5sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 75 antivirus engines flagged the file, including Microsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 7 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: sniffcraft-windows-1.21.11 (1).exe — df2bb8c1603ec386f71ef74bd68dd0d38cc4cd56c2e59b438a386c7eed9f9096
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\sniffcraft-windows-1.21.11.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\sniffcraft-windows-1.21.11.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: conf.json — C:\Users\<USER>\Desktop\conf.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: conf.json — C:\Users\user\Desktop\conf.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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
1 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
- sniffcraft-windows-1.21.11 (1).exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 5.8 MB
- Last analyzed
- Aug 4, 2026, 6:53 AM UTC
df2bb8c1603ec386f71ef74bd68dd0d38cc4cd56c2e59b438a386c7eed9f9096Safety & 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 run 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 developer's official site or an official app store.
- 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 sniffcraft-windows-1.21.11 (1).exe safe, or is it malware?
What is sniffcraft-windows-1.21.11 (1).exe?
How many antivirus engines detected sniffcraft-windows-1.21.11 (1).exe?
I already downloaded and ran sniffcraft-windows-1.21.11 (1).exe — what should I do?
How do I remove sniffcraft-windows-1.21.11 (1).exe?
What is the SHA-256 hash of sniffcraft-windows-1.21.11 (1).exe?
How up to date is this analysis of sniffcraft-windows-1.21.11 (1).exe?
Community
Member reviews and reports for this exact file hash.