Is Compet.exe safe?
Only 3 of 75 engines raised generic concerns, while all 17 reporting tier-1 engines and one completed sandbox supplied no corroborating malicious finding.
Three of 75 engines flagged this executable, but none of the 17 reporting tier-1 engines detected it and no family consensus formed. One completed sandbox found no malicious outcome or offensive-only technique, making the sparse generic detections more consistent with false positives, though the unsigned and newly observed file still warrants source verification.
13631c87611848a653…17b7bf8f0b2474Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
Three of 75 engines flagged this executable, but none of the 17 reporting tier-1 engines detected it and no family consensus formed. One completed sandbox found no malicious outcome or offensive-only technique, making the sparse generic detections more consistent with false positives, though the unsigned and newly observed file still warrants source verification.
The detection rate is low at 3 of 75 engines, with no tier-1 detections or family consensus. Skyhigh contributes the strongest counter-signal through a generic behavior-based backdoor label, while APEX and Cylance offer broad labels without a named family. One completed sandbox produced no malicious verdict, no offensive-only behavior, no persistence indicators, and no dropped files. Static analysis found no packer or high-entropy code, and researcher intelligence produced no matching rules or known-malicious record. Confidence is moderated because the executable is unsigned, newly submitted, and has no signer or similar-file history.
What We Detected
Three of 75 engines raised alerts. Skyhigh reported a generic behavior-based backdoor label, while APEX and Cylance used broad non-family labels. None of the 17 reporting tier-1 engines detected the sample, and no malware-family consensus formed.
Threat Behavior
One completed sandbox run produced no malicious verdict and recorded no offensive-only techniques, persistence indicators, dropped files, or network contacts. The observed MITRE techniques were ambient activities that can also occur in ordinary software. Static PE analysis found no identified packer, likely packing, or high-entropy code section. No complete contacted-host reputation cross-check was available, though the sandbox recorded no hosts to evaluate.
What To Do Now
Confirm that the file came from the expected developer or official distribution channel before running it, because it is unsigned and newly observed. Keep endpoint protection enabled and consider retesting after engines have had more time to analyze the hash if the source cannot be verified.
Where this verdict could be wrong3 caveats
- The executable is unsigned and was first submitted 0 days ago, so its provenance and longer-term reputation remain unestablished.
- Skyhigh supplied one tier-2 behavior-based backdoor detection, which is stronger than the two low-trust generic labels but lacks corroboration.
- contactedHosts=null, although the completed sandbox recorded no contacted domains, IPs, or URLs; no independent host-reputation cross-check was available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- All 17 reporting tier-1 engines returned no detection
- One completed sandbox produced no malicious verdict
- No offensive-only techniques, persistence, or dropped files were observed
- No packer or high-entropy code was identified
- No MalwareBazaar, CIRCL, or YARAify hit was present
- Unsigned Win32 executable with no established signer history
- First submitted 0 days ago, leaving little reputation history
- Skyhigh behavior-based generic backdoor detection
- Two additional generic detections from APEX and Cylance
Use the file only if its download source and expected publisher can be independently verified. Keep endpoint protection enabled, and avoid execution if the origin is uncertain.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 10MITRE ATT&CK techniques
- 2spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
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.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 3 / 75engines flagged
- 4sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 of 75 antivirus engines flagged the file, including APEX and Cylance.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 4 times from 4 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Compet.exe — 13631c87611848a65391dbc02eeba7581ea878af5a680bab4417b7bf8f0b2474
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\file.exe"
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
3 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
- Compet.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 2.0 MB
- Last analyzed
- Sep 25, 2026, 8:19 AM UTC
13631c87611848a65391dbc02eeba7581ea878af5a680bab4417b7bf8f0b2474Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is Compet.exe safe?
What is Compet.exe?
How many antivirus engines detected Compet.exe?
What is the SHA-256 hash of Compet.exe?
Is it safe to run Compet.exe?
How up to date is this analysis of Compet.exe?
Community
Member reviews and reports for this exact file hash.