Is python-manager-26.3.msix safe?
No antivirus engine detected malware, but unsigned packaging and sandbox indicators involving T1055 and LSASS warrant source verification before installation.
All 75 antivirus engines avoided a malware or suspicious detection, including 16 tier-1 engines, and the completed sandbox did not issue a malicious finding. However, the unsigned package produced T1055 and LSASS-related indicators, while its six extracted children remain individually unresolved, so installation should be limited to a verified official source.
bdd1a4e0b485f67474…abb2661e3badecRecommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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 avoided a malware or suspicious detection, including 16 tier-1 engines, and the completed sandbox did not issue a malicious finding. However, the unsigned package produced T1055 and LSASS-related indicators, while its six extracted children remain individually unresolved, so installation should be limited to a verified official source.
The strongest evidence is the complete absence of detections across 75 antivirus engines, with no high-trust engine flagging the package. One completed sandbox did not produce a malicious verdict, and the fully checked observed domain had no cached malicious or suspicious reputation. However, runtime telemetry mapped activity to T1055 and surfaced an LSASS-related credential-access heuristic, which is unusual enough to prevent an unqualified benign assessment. The package is also unsigned despite signing being meaningful for this format, and all six extracted children remain unresolved individually. Its circulation across 3,725 sources and 10,657 submissions lowers the likelihood of a newly distributed targeted threat, but provenance should still be verified.
What We Detected
None of 75 antivirus engines flagged the package, including 16 tier-1 engines that reported no detection. The file has substantial circulation, with 3,725 sources and 10,657 submissions. It is unsigned, however, so there is no verified publisher identity or trusted signer history.
Threat Behavior
One completed sandbox run did not issue a malicious verdict. Runtime telemetry nevertheless mapped activity to MITRE T1055 and generated an LSASS-related credential-access heuristic. These indicators can reflect intrusive behavior, although the available evidence does not establish the exact injection method or malicious intent. The single observed domain was covered by the host-reputation check without a malicious or suspicious cache hit, while six extracted children had no malicious finding but remain individually unresolved.
What To Do Now
Confirm that the package hash and download location match the software vendor's official release channel before installing it. Keep endpoint protection enabled, and avoid running the package if its origin cannot be verified; an isolated test environment is appropriate if further validation is required.
Where this verdict could be wrong3 caveats
- signing.applicable=true but signing.signed=false, leaving no verified publisher identity or signer history.
- T1055 and the LSASS-related heuristic can indicate process injection or credential-access activity, despite the non-malicious sandbox outcome.
- The six dropped children have unknown verdicts, so hasMaliciousChild=false does not establish that each child is benign.
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/75 antivirus engines reported malicious or suspicious results
- 16 tier-1 engines reported no detection
- One completed sandbox produced no malicious verdict
- No malicious child was identified among six inspected hashes
- Observed domain reputation coverage found no cached malicious or suspicious hit
- Unsigned package despite signing.applicable=true
- Runtime evidence includes MITRE T1055
- Credential-dumper heuristic references lsass.exe
- Six extracted child hashes remain individually unknown
- No established signer history
Install only after confirming the SHA-256 and download source against an official vendor release. Keep endpoint protection enabled and use an isolated environment if 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
Partial1 of 2 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
- 10MITRE ATT&CK techniques
- 13spawned processes
- 2network contacts
- 17filesystem & 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Moderate concern: Checks which security software you have installed.
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
python-manager-26.3.msix
bdd1a4e0b485f674748b275095cc8e7132beb37a1ae91db080abb2661e3badec
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass C:\ci0c9cu1\data\msix.ps1 C:\Users\<USER>\Desktop\python-manager-26.3.msix
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
Windows PowerShell.lnk
C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
04Isolated runtime analysis - Written fileObserved
ZP1U5A7FWDA2REKR0NCT.temp
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\ZP1U5A7FWDA2REKR0NCT.temp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
assets.msn.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.
- assets.msn.com
- 162.159.36.2
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{72853161-30C5-4D22-B7F9-0BBC1D38A37E}\iexplore\Count
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{72853161-30C5-4D22-B7F9-0BBC1D38A37E}\iexplore\Time
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Ext\Stats\{72853161-30C5-4D22-B7F9-0BBC1D38A37E}\iexplore\Type
- HKEY_USERS\S-1-5-21-575823232-3065301323-1442773979-1000\Software\Microsoft\Internet Explorer\Toolbar\Locked
- C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\ZP1U5A7FWDA2REKR0NCT.temp
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFf925.TMP
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFf925.TMP
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\AppContainerNamedObjects\S-1-15-2-2473817148-3930944034-1235795307-187980641-3967865409-1804095407-1113801530\Local\SM0:7164:304:WilStaging_02
- \Sessions\1\AppContainerNamedObjects\S-1-15-2-2473817148-3930944034-1235795307-187980641-3967865409-1804095407-1113801530\DBWinMutex
- \Sessions\1\AppContainerNamedObjects\S-1-15-2-2473817148-3930944034-1235795307-187980641-3967865409-1804095407-1113801530\Local\SessionImmersiveColorMutex
- \Sessions\1\AppContainerNamedObjects\S-1-15-2-2473817148-3930944034-1235795307-187980641-3967865409-1804095407-1113801530\Local\SM0:7164:120:WilError_03
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- 168561fb18f8eba8043f…740e3fNever scannednever seen before
- 9b3cb225e50034475a21…2f3365Never scannednever seen before
- 16997134e8eb21f83bd8…5e929cNever scannednever seen before
- 864766685bb4a793e4ed…8b8825Never scannednever seen before
- 6ad65ed2cfbe4dc41b57…3511e5Never 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
- 3,725sources 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 10,657 times from 3,725 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: python-manager-26.3.msix — bdd1a4e0b485f674748b275095cc8e7132beb37a1ae91db080abb2661e3badec
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass C:\ci0c9cu1\data\msix.ps1 C:\Users\<USER>\Desktop\python-manager-26.3.msix
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Windows PowerShell.lnk — C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ZP1U5A7FWDA2REKR0NCT.temp — C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\ZP1U5A7FWDA2REKR0NCT.temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: assets.msn.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — 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
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
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- python-manager-26.3.msix
- Format
- ZIP
- Code signing
- No verified publisher
- Size
- 44.9 MB
- Last analyzed
- Sep 27, 2026, 6:31 AM UTC
bdd1a4e0b485f674748b275095cc8e7132beb37a1ae91db080abb2661e3badecSafety & 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 install 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. Download a fresh installer 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 python-manager-26.3.msix safe, or is it malware?
What is python-manager-26.3.msix?
How many antivirus engines detected python-manager-26.3.msix?
What should I do if I already installed python-manager-26.3.msix?
How do I remove python-manager-26.3.msix?
What is the SHA-256 hash of python-manager-26.3.msix?
How up to date is this analysis of python-manager-26.3.msix?
Community
Member reviews and reports for this exact file hash.