Is Sugar Lust - Hentai Harem.exe safe?
Unsigned executable with two YARA rule hits and direct-IP traffic but zero AV detections.
No antivirus engine flagged the file, yet two community YARA rules matched and the sample contacted 14 IPs without domain resolution. The unsigned status and missing host-reputation data leave the risk unresolved.
b30dc819d0d632439b…f2d5aa35307b31Recommended 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.
No antivirus engine flagged the file, yet two community YARA rules matched and the sample contacted 14 IPs without domain resolution. The unsigned status and missing host-reputation data leave the risk unresolved.
Zero detections across 76 engines and tier-1 silence argue against active malware classification. However, the YARAify matches on a Cobalt Strike rule and a debugger-check rule, combined with direct-IP traffic and an unsigned PE, create conflicting signals. The file is common_old with 225 submitters, yet the absence of a contactedHosts reputation check prevents confirming whether the IPs are malicious. Similar imphash matches were inconclusive because they lacked signer correlation. These mixed indicators place the sample in the suspicious band.
What We Detected
76 engines scanned the sample; none returned a malicious result. Two YARA rules from YARAify matched: cobalt_strike_tmp01925d3f and DebuggerCheck__API. The executable is unsigned and contacted 14 IP addresses directly without domain names.
Threat Behavior
One sandbox recorded ambient techniques (T1071, T1082, T1083, T1129, T1574.002) but no offensive MITRE techniques and no malicious sandbox verdict. No dropped children or persistence indicators were observed. Host reputation for the contacted IPs is unavailable.
What To Do Now
Do not execute the file. Keep endpoint protection enabled. If the file must be used, run it in an isolated environment and monitor outbound connections to the listed IPs.
Where this verdict could be wrong2 caveats
- YARAify hit on cobalt_strike_tmp01925d3f could indicate Cobalt Strike loader, but no engine detection and unsigned status leave the signal ambiguous.
- Direct-IP traffic flagged by MalwareTips.Synth.DirectIpC2 may be benign installer behaviour; without contactedHosts reputation the C2 hypothesis cannot be confirmed.
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/76 engines flagged malicious
- common_old prevalence (225 sources)
- no malicious sandbox verdict
- Unsigned Win32 executable
- YARA rule match on cobalt_strike_tmp01925d3f
- Direct-IP traffic to 14 addresses
- contactedHosts reputation check unavailable
Treat the file as suspicious pending further host-reputation data or additional sandbox runs; keep all security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 signature or behavior rules 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
- 5MITRE ATT&CK techniques
- 5spawned processes
- 20network contacts
- 0filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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.
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
Sugar Lust - Hentai Harem.exe
b30dc819d0d632439b16ba324645d03d9d61e3e06fad1d0918f2d5aa35307b31
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\b30dc819d0d632439b16ba324645d03d9d61e3e06fad1d0918f2d5aa35307b31.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\UI0Detect.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.34
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
52.154.209.174
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.
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.
- 192.168.0.34
- 52.154.209.174
- 23.216.81.152
- a83f:8110:ffff:ffff:ffff:ffff:ffff:ffff
- 20.99.186.246
- 23.216.147.64
- 192.168.0.60
- 131.253.33.203
- a83f:8110:1a44:69ff:1943:68ff:1842:65ff
- 192.168.0.24
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 0 / 76engines flagged
- 225sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
0 of 76 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 225 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: Sugar Lust - Hentai Harem.exe — b30dc819d0d632439b16ba324645d03d9d61e3e06fad1d0918f2d5aa35307b31
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\b30dc819d0d632439b16ba324645d03d9d61e3e06fad1d0918f2d5aa35307b31.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\UI0Detect.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 192.168.0.34 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 52.154.209.174 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- cobalt_strike_tmp01925d3f
- DebuggerCheck__API
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.
Evidence52.154.209.174 · 23.216.81.152 · a83f:8110:ffff:ffff:ffff:ffff:ffff:ffff
0 of 76 engines flagged this file
View all 76 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Sugar Lust - Hentai Harem.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 656.5 KB
- Last analyzed
- Jul 26, 2026, 1:52 AM UTC
b30dc819d0d632439b16ba324645d03d9d61e3e06fad1d0918f2d5aa35307b31Safety & 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 Sugar Lust - Hentai Harem.exe safe, or is it malware?
What is Sugar Lust - Hentai Harem.exe?
How many antivirus engines detected Sugar Lust - Hentai Harem.exe?
What should I do if I already ran Sugar Lust - Hentai Harem.exe?
How do I remove Sugar Lust - Hentai Harem.exe?
What is the SHA-256 hash of Sugar Lust - Hentai Harem.exe?
How up to date is this analysis of Sugar Lust - Hentai Harem.exe?
Community
Member reviews and reports for this exact file hash.