Our call: Is setup.exe safe?Malicious
Five tier-1 engines flag this newly submitted installer as Wacatac/Evo-gen with direct-IP contact to an unknown host.
- 13 of 75 antivirus engines flagged the file, including AhnLab-V3 and Avast.Observed · Antivirus analysis
- The hash has been submitted 2 times from 2 sources.Derived · Saved report facts
43842e19dbc8d5b8eb…014e55af7dRecommended next actions
Before installing
Do not install it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already installed it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete13 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
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
setup.exe
43842e19dbc8d5b8eb46bc8c122adae3380ac5021278158dc74b0d014e55af7d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\Google\Chrome\Application\chrome.exe" piggybc.cyou/api/set_agent?id=06A5DA469A8671CB520BAC2B3378888F&token=31c26cc4b34ad35cc35977cceb4da505dece03&description=&agent=Chrome
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
64.89.161.173
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
piggybc.cyou
Contact observed during runtime.
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.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
13 of 75 antivirus engines flagged the file, including AhnLab-V3 and Avast.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: setup.exe — 43842e19dbc8d5b8eb46bc8c122adae3380ac5021278158dc74b0d014e55af7d
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\user\Desktop\setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Program Files\Google\Chrome\Application\chrome.exe" piggybc.cyou/api/set_agent?id=06A5DA469A8671CB520BAC2B3378888F&token=31c26cc4b34ad35cc35977cceb4da505dece03&description=&agent=Chrome
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: 64.89.161.173 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: piggybc.cyou — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
Thirteen of 75 engines, including five tier-1 detections, label the file malicious with generic infostealer families. The sample is signed by an unknown publisher, shows T1005 data-collection behaviour, and contacts an IP address with no prior reputation.
Multiple tier-1 engines converge on malicious labels despite the absence of a strong family consensus. The signer 'bodelan.in' has no history and the certificate is marked invalid. Sandbox telemetry shows direct-IP contact to 64.89.161.173 and a URL on piggybc.cyou, which the DirectIpC2 heuristic flags as suspicious. The file is rare_new with zero prior submissions, eliminating any benign reputation baseline. No sandbox verdict or cached malicious host contradicts the engine findings, but the tier-1 detections outweigh those gaps.
What We Detected
Thirteen engines across our network flagged the 3.2 MB installer. Five tier-1 products (Avast, AVG, Avira, F-Secure, Microsoft, Symantec) returned labels such as Win32:Evo-gen, TR/W32.Evo, and Trojan:Win32/Wacatac.B!ml. Three additional engines referenced Lumma or LummaC2 variants.
Threat Behavior
The executable exhibits T1005 data-collection techniques and reaches out to IP 64.89.161.173 and the domain piggybc.cyou. A single sandbox run recorded these contacts but did not produce an explicit malicious verdict. The certificate is signed by 'bodelan.in' with no prior samples on record.
What To Do Now
Do not execute the file. Keep endpoint protection enabled and submit the sample to your security vendor for deeper analysis if further confirmation is required.
Where this verdict could be wrong3 caveats
- contactedHosts.maliciousHosts.length=0 — inspected host 64.89.161.173 not previously flagged in our cache
- behaviour.hasMaliciousSandboxVerdict=false — single sandbox run produced no explicit malicious verdict
- engines.tier1FamilyConsensus.strong=false — only one tier-1 engine agreed on 'attribute' family
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- contacted host not previously flagged malicious
- no dropped malicious children
- sandbox produced no explicit malicious verdict
- Five tier-1 malicious detections
- Unknown signer with invalid signature
- Direct-IP contact to unclassified host
- Zero prior reputation (rare_new)
Block or delete the file; the combination of tier-1 detections and direct-IP behaviour outweighs the lack of cached host reputation.
Behavior
Plain-English impact first, then the observed runtime evidence.
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Communicates over the network in a non-standard way.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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.
Threat context
How info-stealers work
An info-stealer runs quietly in the background and copies your private data — saved passwords, browser cookies, autofill details, and crypto wallets — then sends it to criminals. You usually won't notice anything is wrong.
Bottom line:Stolen logins are used to break into your accounts or sold in bulk on criminal markets.
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.
- 64.89.161.173
- http://piggybc.cyou/
- App9DEB9A3255D0154F
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Detection sources at a glance
Category: infostealer
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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.
Evidence64.89.161.173
13 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
Barely seen in the wild and first surfaced recently. 13 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- setup.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: bodelan.in
- Size
- 3.1 MB
- Last analyzed
- Aug 1, 2026, 4:30 PM UTC
43842e19dbc8d5b8eb46bc8c122adae3380ac5021278158dc74b0d014e55af7dSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
Don't install this file. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already installed it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
Download a fresh installer from the developer's official site or an official app store.