Is PROGMAN.EXE safe?
Unsigned legacy Windows component with two low-trust detections and an NSRL reference entry.
Two low-trust engines flagged the file; no tier-1 consensus exists. The sample matches an NSRL-listed Windows XP program manager and carries a researcher note calling it safe.
a12739dc6252b8952a…f7f86dca3be134Recommended 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.
Two low-trust engines flagged the file; no tier-1 consensus exists. The sample matches an NSRL-listed Windows XP program manager and carries a researcher note calling it safe.
The engine results show only low-trust detections and no tier-1 agreement. The file is unsigned, yet its age, medium prevalence, and NSRL reference indicate a known legacy component rather than new malware. Sandbox activity includes T1055, but the single sandbox returned no malicious verdict and the contacted-host reputation check is incomplete. Community annotation explicitly labels the file safe.
What We Detected
Two of 76 engines (APEX, Sangfor) returned malicious labels; none are tier-1. The file is an unsigned Win32 EXE first seen in 2010 and listed in the NSRL reference database.
Threat Behavior
Sandbox execution recorded MITRE T1055 process-injection calls and direct-IP traffic, but no malicious sandbox verdict or dropped malicious children. No domains were contacted and the host-reputation cross-check was not completed.
What To Do Now
Keep endpoint protection enabled. The file appears to be a rewritten Windows XP program manager; if you do not need it, leave it quarantined or delete it.
Where this verdict could be wrong1 caveat
- T1055 process-injection technique observed in sandbox run, but no tier-1 engine consensus and NSRL reference entry supports legacy Windows component.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- NSRL reference entry
- Medium prevalence over 15 years
- Researcher comment labels file safe
- Unsigned executable
- Process-injection technique observed in sandbox
The evidence supports treating the file as benign legacy software; retain normal antivirus protection and avoid running unknown executables.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial9 runtime contacts were observed without a completed reputation cross-check.
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
- 16MITRE ATT&CK techniques
- 2spawned processes
- 9network contacts
- 7filesystem & mutex artifacts
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
PROGMAN.EXE
a12739dc6252b8952a5219526382a45ac1659b94e5d56eff7ef7f86dca3be134
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\PROGMAN.EXE
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\PROGMAN.EXE"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
192.168.0.9
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- 204.79.197.203
- 192.168.0.9
- 151.101.22.172
- 23.216.81.152
- 192.168.0.1
- 192.168.0.133
- 20.99.133.109
- 184.27.218.92
- 64.4.10.33
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
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
- 2 / 76engines flagged
- 13sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash appears in a known-software reference database.
Verdict inputView chapterProvenanceObservedSourceReference software databaseObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
2 of 76 antivirus engines flagged the file, including APEX and Sangfor.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: PROGMAN.EXE — a12739dc6252b8952a5219526382a45ac1659b94e5d56eff7ef7f86dca3be134
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\PROGMAN.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\PROGMAN.EXE"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 192.168.0.9 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
Evidence%SAMPLEPATH%\PROGMAN.EXEThe 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.
Evidence204.79.197.203 · 151.101.22.172 · 23.216.81.152
2 of 76 engines flagged this file
View all 76 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
- PROGMAN.EXE
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 201.0 KB
- Last analyzed
- Aug 19, 2026, 3:46 AM UTC
a12739dc6252b8952a5219526382a45ac1659b94e5d56eff7ef7f86dca3be134Safety & 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 PROGMAN.EXE safe?
What is PROGMAN.EXE?
How many antivirus engines detected PROGMAN.EXE?
What is the SHA-256 hash of PROGMAN.EXE?
Is it safe to run PROGMAN.EXE?
How up to date is this analysis of PROGMAN.EXE?
Community
Member reviews and reports for this exact file hash.