Is FontCreator.exe safe?
Five community YARA matches and possible T1055 process injection outweigh sparse generic detections, but absent tier-one consensus prevents a definitive malware-family attribution.
The strongest concerns are five community YARA matches, including injection and packed-malware rules, plus runtime evidence mapped to T1055. However, only 3 of 75 engines flagged the file, all 17 reporting tier-one engines were clean, and the single sandbox produced no malicious verdict, leaving materially mixed evidence.
f41b316b333216f41c…b4c1621221adcfRecommended 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.
The strongest concerns are five community YARA matches, including injection and packed-malware rules, plus runtime evidence mapped to T1055. However, only 3 of 75 engines flagged the file, all 17 reporting tier-one engines were clean, and the single sandbox produced no malicious verdict, leaving materially mixed evidence.
Five community YARA rules matched, which is strong corroborating static evidence, although several rules focus on MPRESS and TLS-callback characteristics rather than one identified family. One completed sandbox run mapped activity to T1055 process injection and recorded a direct IP contact, but it did not issue a malicious runtime verdict. Only 3 of 75 engines detected the executable, with no tier-one detections or family consensus. The executable is unsigned, so no authenticated publisher history offsets the concerning evidence. Host reputation was not checked or saved, and the four dropped files remain without individual verdicts, limiting confidence in both directions.
What We Detected
Three of 75 antivirus engines flagged the executable: Elastic, Malwarebytes, and Trapmine. Their labels are generic or heuristic, while all 17 reporting tier-one engines were clean and no engine family consensus formed. More importantly, five community YARA rules matched, including CP_Script_Inject_Detector, two MPRESS-related rules, pe_detect_tls_callbacks, and TeslaCryptPackedMalware. These matches raise concern, but some may reflect packing or implementation traits rather than a specific malware family.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055, indicating possible process injection, and observed a direct connection to 162.159.36.2. The sandbox itself did not produce a malicious verdict, and the T1055 mapping does not establish the exact injection method or intent. No complete host-reputation result is available because contactedHosts was not checked or saved. Four dropped hashes were inspected without a malicious child finding, although each child still lacks a final individual verdict.
What To Do Now
Do not run this copy on a production system until its origin and hash are verified against the software publisher's official release channel. Keep endpoint protection enabled, quarantine the file if its source is uncertain, and use an isolated analysis environment if further examination is necessary.
Where this verdict could be wrong5 caveats
- All 17 reporting tier-1 engines were clean, while the three detections from Elastic, Malwarebytes, and Trapmine used generic or heuristic labels.
- behaviour.hasMaliciousSandboxVerdict=false; the single completed sandbox labeled its run clean.
- droppedChildren.hasMaliciousChild=false, although all four inspected child hashes lacked final verdicts.
- externalIntel.malwareBazaar.hit=false and no named engine family consensus was present.
- Several YARA matches identify MPRESS or TLS-callback traits rather than a specific malware family, so they may reflect packing-related overlap.
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-one engines were clean
- Only 3 of 75 engines flagged the sample
- The completed sandbox produced no malicious verdict
- No malicious dropped child was established
- No engine family consensus or confirmed hacktool label was present
- Five community YARA rules matched, including injection and packed-malware signatures
- Runtime evidence mapped activity to MITRE T1055
- The executable is unsigned and has no signer history
- A direct connection to 162.159.36.2 was observed without a completed reputation check
- Three antivirus engines issued generic or heuristic detections
Quarantine this copy and obtain a fresh installer directly from the publisher's official channel, then verify its hash or signature before use. Keep antivirus and endpoint protection enabled.
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
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete7 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
- 7MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 21filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Reads your Windows user-account details.
Note: Listed running processes; both legitimate software and malware may do this.
Note: Collects details about your system.
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
FontCreator.exe
f41b316b333216f41c776292b5773b11758bef7379ea25d43bb4c1621221adcf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\FontCreator.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\FontCreator.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
license.lock
C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\license.lock
04Isolated runtime analysis - Written fileObserved
settings.json
C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\settings.json
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- HKEY_CURRENT_USER\SOFTWARE\High-Logic\FontCreator\InstallID
- Software\High-Logic\FontCreator\InstallID
- HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
- C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\license.lock
- C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\settings.json
- C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\ETRRNUWE04WDXVFWBHUI.temp
- C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\preview.txt
- C:\ProgramData\High-Logic\Errors\error_uploader.lock
- C:\Users\<USER>\AppData\Local\Temp\FontCreator.madExcept
- C:\Users\<USER>\AppData\Local\Temp
- C:\Users\<USER>\AppData\Local\Temp\FontCreator.madExcept\
- C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\license.lock
- C:\Users\<USER>\AppData\Local\Temp\FontCreator.madExcept\.
- madExceptSettingsMtx$1558
- HookTThread$1558
- HLFontCreator16
- Global\TMainFormFontCreator
- \Sessions\1\BaseNamedObjects\madExceptSettingsMtx$1990
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- ef8fb39ef851d228d6a3…299b3bNever scannednever seen before
- f9c746d5a455528db6e4…71bb05Never scannednever seen before
- ab1728555241f050dd3a…fafcd8Never scannednever seen before
- e3b0c44298fc1c149afb…52b855Never 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.
- 7rule hits recorded
- 3 / 75engines flagged
- 28sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
3 of 75 antivirus engines flagged the file, including Elastic and Malwarebytes.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
YARAify matched 5 researcher rules to this file.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: FontCreator.exe — f41b316b333216f41c776292b5773b11758bef7379ea25d43bb4c1621221adcf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\FontCreator.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\FontCreator.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: license.lock — C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\license.lock
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: settings.json — C:\Users\<USER>\AppData\Roaming\High-Logic\FontCreator\16.0\settings.json
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
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.
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.
- CP_Script_Inject_Detector
- INDICATOR_EXE_Packed_MPress
- mpress_2_xx_x64
- pe_detect_tls_callbacks
- TeslaCryptPackedMalware
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"C:\Users\<USER>\Desktop\FontCreator.exe"The 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.
Evidence162.159.36.2
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
- FontCreator.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 10.5 MB
- Last analyzed
- Oct 7, 2026, 2:33 PM UTC
f41b316b333216f41c776292b5773b11758bef7379ea25d43bb4c1621221adcfSafety & 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 FontCreator.exe safe, or is it malware?
What is FontCreator.exe?
How many antivirus engines detected FontCreator.exe?
I already downloaded and ran FontCreator.exe — what should I do?
How do I remove FontCreator.exe?
What is the SHA-256 hash of FontCreator.exe?
How up to date is this analysis of FontCreator.exe?
Community
Member reviews and reports for this exact file hash.