Is msdot.exe safe?
Twenty-three of 75 engines flagged this unsigned, packed executable, with multiple established products naming Yogi and four independent tier-1 detections overall.
The file drew 23 detections from 75 engines, including four independent tier-1 detections. Multiple products identify Yogi, while the unsigned, packed structure and near-zero prevalence reinforce concern, although no completed runtime analysis is available.
cc7d0cb64ac4fc4bfc…eea4573be63d59Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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 file drew 23 detections from 75 engines, including four independent tier-1 detections. Multiple products identify Yogi, while the unsigned, packed structure and near-zero prevalence reinforce concern, although no completed runtime analysis is available.
A substantial 23 of 75 engines detected the executable, and four independent tier-1 engines contributed malicious findings. BitDefender, Emsisoft, and GData use the Yogi label, while ESET-NOD32 and Ikarus identify generic Agent trojans. The executable is unsigned, newly observed, and contains a high-entropy packed code section, which strengthens the static detections. The exact family attribution carries some uncertainty because the independent tier-1 family consensus is not strong and several tier-1 engines remained silent. No completed sandbox observation or complete contacted-host reputation result is available, so the assessment rests primarily on static and antivirus evidence.
What We Detected
Twenty-three of 75 antivirus engines flagged msdot.exe. Four independent tier-1 detections are present, with BitDefender, Emsisoft, and GData reporting the Yogi label and ESET-NOD32 identifying WinGo/Agent.BDI.
Threat Behavior
The executable is unsigned and appears packed, with peAnalysis.highEntropyCode=true and a UPX1 section entropy of 7.92. It has been seen from only one source in one submission, offering no established distribution history. No completed runtime observation is available, and host-reputation coverage was not completed or saved, so execution and network behavior cannot be characterized.
What To Do Now
Do not run the file on a production or personal system. Keep endpoint protection enabled, quarantine or remove the sample, and obtain a fresh copy only from a verified official source if the program was expected.
Where this verdict could be wrong4 caveats
- engines.tier1FamilyConsensus.strong=false, and the Yogi family has only one independent tier-1 consensus vote despite several product labels.
- 11 tier-1 engines reported no detection, including Avast, AVG, Avira, DrWeb, F-Secure, and Fortinet.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false; these absences may reflect coverage gaps rather than exoneration.
- No runtime evidence is available because behaviour=null, and contactedHosts=null means network reputation was not completely checked.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 11 tier-1 engines reported no detection
- No malicious child file was reported
- No YARAify, CIRCL, or MalwareBazaar corroboration was found
- No brand mismatch was detected
- 23/75 antivirus detections
- Four independent tier-1 detections
- Multiple engines identify the Yogi family
- Unsigned Windows executable
- High-entropy packed code
- Only one source and one submission
Quarantine the executable and do not launch it. Keep security protection enabled and replace it only with a copy obtained directly from a verified publisher channel.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete23 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
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
- 23 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
23 of 75 antivirus engines flagged the file, including ALYac and APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at
Detection sources at a glance
Category: generic-trojan
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.
PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code section
23 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 23 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- msdot.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 14.1 MB
- Last analyzed
- Oct 4, 2026, 6:32 PM UTC
cc7d0cb64ac4fc4bfc1c5ea6b4f9bbc701336ef8fb6b35a545eea4573be63d59Safety & 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.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran 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.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is msdot.exe malware?
What is msdot.exe?
How many antivirus engines detected msdot.exe?
I already downloaded and ran msdot.exe — what should I do?
How do I remove msdot.exe?
What kind of malware is msdot.exe?
What is the SHA-256 hash of msdot.exe?
How up to date is this analysis of msdot.exe?
Community
Member reviews and reports for this exact file hash.