Is AntiPublic.exe safe?
Only two low-trust engines raised generic alerts, but unsigned provenance and unresolved direct-IP activity prevent confidently treating this executable as benign.
The two detections among 75 engines are generic and limited to low-trust scanners, making a false positive more likely than established malware. However, the unsigned executable contacted two IP addresses directly, and no complete reputation check is available for those hosts, so caution remains appropriate.
69108b4c5b6345ca2f…6328921512e0bcRecommended 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.
The two detections among 75 engines are generic and limited to low-trust scanners, making a false positive more likely than established malware. However, the unsigned executable contacted two IP addresses directly, and no complete reputation check is available for those hosts, so caution remains appropriate.
APEX and Bkav are the only engines flagging the sample, while no tier-1 engine identifies malware or agrees on a family. That detection pattern usually indicates heuristic false positives. One completed sandbox run recorded direct connections to two IP addresses and mapped T1486, but it produced no malicious sandbox verdict. The IP addresses were not covered by a saved host-reputation check, so their risk remains unresolved. The executable is unsigned and lacks publisher history, while ten inspected dropped files were not identified as malicious. Overall, the evidence is mixed and does not establish a malware family.
What We Detected
APEX and Bkav flagged the file, giving a total of 2 detections among 75 engines. Both are low-trust detections with generic labels, while tier-1 engines did not identify a malware family. The executable is unsigned and has no established signer history.
Threat Behavior
One sandbox run observed connections to 20.99.133.109 and 184.27.218.92 and mapped technique T1486. No malicious sandbox verdict was produced, and none of the ten inspected dropped children was marked malicious. Because contactedHosts is unavailable, there is no complete reputation result for the observed IP addresses.
What To Do Now
Do not run the file on a production or personal system until its source and expected purpose are verified. Keep endpoint protection enabled, obtain a fresh copy from an authoritative source if possible, and isolate the sample for further network-focused analysis if verification is unavailable.
Where this verdict could be wrong3 caveats
- engines.onlyLowTrustFlagging=true and engines.tier1Malicious=0 make the two generic detections likely false positives.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false after 10 children were inspected.
- externalIntel.malwareBazaar.hit=false and externalIntel.yaraify.ruleCount=0 provide no researcher-curated malware corroboration, although absence of a hit does not prove benignity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 2/75 engines detected the file, both low-trust
- engines.tier1Malicious=0 with no family consensus
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false after 10 children were inspected
- externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false
- Unsigned Win32 executable with no established publisher history
- Direct connections to 20.99.133.109 and 184.27.218.92
- No complete host-reputation result for the contacted IP addresses
- Sandbox mapping includes offensive technique T1486
- Two prior imphash matches received suspicious assessments, although both are weak framework-level matches
Avoid executing it until the source and the two contacted IP addresses can be independently verified. Keep security protections enabled and use an isolated environment for any necessary further testing.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were 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
- 12MITRE ATT&CK techniques
- 3spawned processes
- 2network contacts
- 19filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
AntiPublic.exe
69108b4c5b6345ca2f956ad4467de1c0c4d09ea78635247cc26328921512e0bc
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\AntiPublic.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\AntiPublic.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_avif.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_avif.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_imaging.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
184.27.218.92
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 20.99.133.109
- 184.27.218.92
- C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_avif.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_imagingmath.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_imagingtk.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\83fi9xtz
- C:\Users\<USER>\AppData\Local\Temp\tmpt4luthls\fontlist-v390.json.matplotlib-lock
- C:\Users\<USER>\Desktop\combo_storage.db-journal
- %USERPROFILE%\AppData\Local\Temp\ske5eira
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never scannednever seen before
- 76f6bc85fc9cb89bc3f9…5415eaNever 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
- 2 / 75engines flagged
- 9sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 9 times from 9 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: AntiPublic.exe — 69108b4c5b6345ca2f956ad4467de1c0c4d09ea78635247cc26328921512e0bc
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\AntiPublic.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — %SAMPLEPATH%\AntiPublic.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: _avif.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_avif.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI62482\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 184.27.218.92 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidence20.99.133.109 · 184.27.218.92
2 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
- AntiPublic.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 37.3 MB
- Last analyzed
- Sep 14, 2026, 10:49 PM UTC
69108b4c5b6345ca2f956ad4467de1c0c4d09ea78635247cc26328921512e0bcSafety & 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 AntiPublic.exe safe, or is it malware?
What is AntiPublic.exe?
How many antivirus engines detected AntiPublic.exe?
What should I do if I already ran AntiPublic.exe?
How do I remove AntiPublic.exe?
What is the SHA-256 hash of AntiPublic.exe?
How up to date is this analysis of AntiPublic.exe?
Community
Member reviews and reports for this exact file hash.