Suspicious
ZIP archive extracts and runs unsigned PE files while contacting a direct IP with no DNS resolution.
cc51dea6d98e36e550…8b012ce99aThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
The single DrWeb detection on a medium-prevalence unsigned ZIP is offset by broad tier-1 clean reports and absence of sandbox malice verdicts. Direct-IP C2 without domains plus dropped PE files remain concerning indicators. Overall evidence sits in mixed territory without strong tier-1 consensus or confirmed malicious children.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.topDetections[0]: DrWeb tier1 result Trojan.Starter.8416
behaviour.contactedIps: 162.159.36.2 with zero domains (MalwareTips.Synth.DirectIpC2)
behaviour.offensiveTechniques: T1562.001
droppedChildren.hasMaliciousChild: false (4 children unknown)
prevalence.classification: medium (60 unique sources)
- 14 tier-1 engines reported clean
- No malicious sandbox verdict
- No malicious dropped children
- No external intelligence hits
- Direct IP contact without DNS (MalwareTips.Synth.DirectIpC2)
- T1562.001 impair defenses technique observed
- Unsigned archive with dropped PE children
- Single tier-1 detection on medium-prevalence file
Treat as suspicious; quarantine the archive and monitor endpoints for the extracted Launcher components and the observed direct IP.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Talks to a remote server to take commands or send out your data.
High concern: Tries to disable or bypass your security software.
High concern: Hijacks how Windows loads programs so it runs automatically.
Moderate concern: Checks whether it's being watched in a sandbox before acting.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
starter corroborated by 2 sources
- VT (74 engines)starter
- MT AI Enginestarter
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:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\Users\user\AppData\Local\Temp\fwnolikr.vz2
- C:\Users\user\AppData\Local\Temp\fwnolikr.vz2\Launcher.dll
- C:\Users\user\AppData\Local\Temp\fwnolikr.vz2\Launcher.exe
- C:\Users\user\AppData\Local\Temp\fwnolikr.vz2\Launcher.exe.manifest
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- fb07af2aead3bdf360f5…72ba03Never scannednever seen before
- c5cc6765b2fcacca179c…510903Never scannednever seen before
- f83ba415d9be3e9a0659…836a51Never scannednever seen before
- 557abdcccfb25bdc9363…5542c5Never scannednever seen before
YARA & heuristic rule matches
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 1 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence162.159.36.2
1 detection across 74 engines
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Forensic fingerprint
- File name
- uploaded-file.zip
- Size
- 178.9 KB
- MIME type
- (unknown)
- Detected type
- ZIP
- SHA-256
- cc51dea6d98e36e550a72f3a3bce93204ef1989840b02b1157df8a8b012ce99a
- MD5
- 4f4afce0dcf508aacf97889e59da70e5
- SHA-1
- c6a3115e824b9eccaffd5e8635b16fc66b457409
- First seen (VT)
- 6/12/2026, 3:51:37 PM UTC
- Last analysis (VT)
- 7/11/2026, 1:28:27 AM UTC
- First scan (MalwareTips)
- 7/15/2026, 7:27:03 AM UTC
- Last scan (MalwareTips)
- 7/15/2026, 7:27:03 AM UTC
Safety FAQ
Common questions about uploaded-file.zip, answered from the scan data above.
- uploaded-file.zip is suspicious — treat it as unsafe until you're sure. 1 of 74 antivirus engines flag it (family: starter), which isn't a strong consensus but is enough to be cautious. Don't opened or extracted it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- uploaded-file.zip is a compressed archive, about 179 KB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- 1 of 74 antivirus engines flagged uploaded-file.zip, 1 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove uploaded-file.zip: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original uploaded-file.zip file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- uploaded-file.zip is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the starter family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
- The SHA-256 hash of uploaded-file.zip is cc51dea6d98e36e550a72f3a3bce93204ef1989840b02b1157df8a8b012ce99a, and its MD5 is 4f4afce0dcf508aacf97889e59da70e5. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 15, 2026. Because a file's hash never changes, the identity of uploaded-file.zip is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.