Is MSPCity.exe safe?
No antivirus engine detected this unsigned executable, but recorded process-injection and LSASS-targeting indicators warrant caution until its origin and behavior are independently verified.
All 75 antivirus engines returned no detection, and the completed sandbox did not issue a malware finding. However, the unsigned executable produced indicators associated with process injection and LSASS access, so the clean engine results are not enough to dismiss the runtime concerns.
63f20c462a6396517e…274a7534807148Recommended 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.
All 75 antivirus engines returned no detection, and the completed sandbox did not issue a malware finding. However, the unsigned executable produced indicators associated with process injection and LSASS access, so the clean engine results are not enough to dismiss the runtime concerns.
The strongest reassuring evidence is that 0 of 75 engines detected the file, including all 17 reporting tier-1 engines. One completed sandbox did not assign a malware finding, and no inspected child was identified as malicious. Against that, runtime evidence mapped activity to T1055 and recorded LSASS targeting, alongside several other offensive techniques. The executable is unsigned and has no publisher history to establish provenance. Similar files sharing its imphash were previously treated cautiously, though those imphash-only matches are weak because they lack signer co-matches. Taken together, the evidence supports containment and source verification rather than ordinary execution.
What We Detected
None of 75 antivirus engines flagged the executable, and all 17 reporting tier-1 engines were non-detecting. The file is nevertheless unsigned, with no verified publisher or historical signer record. Five prior files sharing imphash b34f154ec913d2d2c435cbd644e91687 received cautious assessments, but those matches involved different signer contexts and may reflect a shared installer framework rather than a common payload.
Threat Behavior
The completed runtime observation mapped activity to T1055, T1134, T1485, T1486, and T1548. Saved heuristic evidence specifically identifies possible process injection involving Explorer and process activity targeting LSASS, which can be associated with credential access. The sandbox itself did not issue a malware finding, and none of 10 inspected dropped children was identified as malicious, although their individual verdicts remain unknown. Eight contacted hosts had no cached malicious or suspicious match, but this check did not cover every distinct domain and IP recorded during execution, so no complete host-reputation conclusion is available.
What To Do Now
Do not run the executable on a production or personal system until its download source and expected publisher are verified. Keep endpoint protection enabled, and if testing is essential, use an isolated disposable environment with no credentials or sensitive data.
Where this verdict could be wrong5 caveats
- All 75 antivirus engines were non-detecting, including 17 tier-1 engines, which strongly counters a conventional malware interpretation.
- The completed sandbox assigned a clean result and behaviour.hasMaliciousSandboxVerdict=false.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false, although absent intelligence hits do not prove benignity.
- contactedHosts inspected 8 hosts without a malicious or suspicious cache match, but it did not cover every distinct runtime contact.
- droppedChildren.hasMaliciousChild=false, but the 10 inspected child verdicts are all unknown rather than confirmed clean.
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 of 75 antivirus engines detected the file
- All 17 reporting tier-1 engines were non-detecting
- The completed sandbox did not issue a malware finding
- No inspected dropped child was identified as malicious
- No YARAify, CIRCL, or MalwareBazaar intelligence hit was present
- Unsigned Win32 executable with no verified publisher history
- Runtime evidence mapped to process injection technique T1055
- Saved process activity targeted LSASS
- Five offensive MITRE techniques were recorded
- All 10 dropped-child verdicts remain unknown
- Contacted-host reputation coverage was incomplete
Verify the executable against the publisher's official release channel and checksum before use. Keep security protection enabled and quarantine the file if its provenance cannot be established.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial8 of 19 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 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
- 26MITRE ATT&CK techniques
- 14spawned processes
- 19network contacts
- 33filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
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.
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
MSPCity.exe
63f20c462a6396517ed65dcfe8c4f1d7739f197a3b4c1fd0d6274a7534807148
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\MSPCity 1.0.0.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\System.dll
04Isolated runtime analysis - Written fileObserved
app-64.7z
C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\app-64.7z
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
mspcity.pl
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostDerived
static.cloudflareinsights.com
Saved reputation verdict: safe.
07Contacted-host cross-check - +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.
- mspcity.pl
- static.cloudflareinsights.com
- fpdownload.macromedia.com
- play.mspcity.pl
- redirector.gvt1.com
- r3---sn-p5qlsn76.gvt1.com
- r3.sn-p5qlsn76.gvt1.com
- a1672.dscr.akamai.net
- 172.67.132.159
- 104.16.79.73
- 23.204.184.114
- 159.195.253.199
- 224.0.0.251
- 8.8.8.8
- 172.253.63.113
- 104.21.13.57
- 172.217.135.200
- 224.0.0.252
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Bags\1\Desktop\IconLayouts
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\Shell\Bags\1\Desktop\IconNameVersion
- HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\ApplicationViewManagement\W32:000000000003005A\VirtualDesktop
- HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
- C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\app-64.7z
- C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\nsis7z.dll
- C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\7z-out\locales
- C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\7z-out\resources
- C:\Users\<USER>\AppData\Roaming\MSPCity\Local Storage\leveldb\000001.dbtmp
- C:\Users\<USER>\AppData\Roaming\MSPCity\Code Cache\wasm\index-dir\the-real-index
- C:\Users\<USER>\AppData\Roaming\MSPCity\Code Cache\js\index-dir\the-real-index
- C:\Users\<USER>\AppData\Roaming\MSPCity\17391dfb-76fa-4376-b206-4f48189487ea.tmp
- C:\Users\<USER>\AppData\Roaming\MSPCity\Pepper Data\Shockwave Flash\WritableRoot\#SharedObjects\56A865YP\macromedia.com\support\flashplayer\sys\settings.sxx
- Global\SyncRootManager
- Local\AtomProcessSingletonStartup!
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fbcfe23a2ecb82b7100c…dc0f2dNever scannednever seen before
- ce84676f37bf97078b3d…754f03Never scannednever seen before
- 06b25851b73724deac7c…e3f264Never scannednever seen before
- 7f0b86e4f6391e48fd04…2ec059Never scannednever seen before
- f25c8b41249c8f542247…27c827Never scannednever seen before
- 0823cf9667272ede4cad…089b8eNever scannednever seen before
- 1d1a3e38ddf282969bca…8c94deNever scannednever seen before
- 3eb38ae99653a7dbc724…f2eacaNever scannednever seen before
- ae123e3a680a9c514c44…6d15a9Never scannednever seen before
- 4c8c35f68f26e7ea7cc6…e19c2dNever 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.
- 2rule hits recorded
- 0 / 75engines flagged
- 74sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 87 times from 74 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: MSPCity.exe — 63f20c462a6396517ed65dcfe8c4f1d7739f197a3b4c1fd0d6274a7534807148
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\MSPCity 1.0.0.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: app-64.7z — C:\Users\<USER>\AppData\Local\Temp\nsk1885.tmp\app-64.7z
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: mspcity.pl — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: static.cloudflareinsights.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved 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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
0 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
- MSPCity.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 62.6 MB
- Last analyzed
- Oct 2, 2026, 3:18 PM UTC
63f20c462a6396517ed65dcfe8c4f1d7739f197a3b4c1fd0d6274a7534807148Safety & 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 MSPCity.exe safe, or is it malware?
What is MSPCity.exe?
How many antivirus engines detected MSPCity.exe?
What should I do if I already ran MSPCity.exe?
How do I remove MSPCity.exe?
What is the SHA-256 hash of MSPCity.exe?
How up to date is this analysis of MSPCity.exe?
Community
Member reviews and reports for this exact file hash.