Is sspm_to_txt.exe safe?
Twenty-three of 75 engines detect this unsigned executable, while runtime evidence indicates process injection and LSASS-related activity consistent with a generic trojan.
The executable is flagged by 23 of 75 engines, including four high-trust products, and it lacks a verified signature. Runtime evidence maps activity to process injection, destructive-impact techniques, privilege escalation, and LSASS access; however, the engines do not establish one consistent named family.
0ada0cf0cc90c16bcb…b09a370d1f9e5dRecommended 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 executable is flagged by 23 of 75 engines, including four high-trust products, and it lacks a verified signature. Runtime evidence maps activity to process injection, destructive-impact techniques, privilege escalation, and LSASS access; however, the engines do not establish one consistent named family.
The detection volume is substantial: 23 of 75 engines flag the executable, with Microsoft, Fortinet, Symantec, and TrendMicro-HouseCall contributing four high-trust detections. Labels vary between Wacatac, ABTrojan, generic trojan, and machine-learning assessments, so the evidence supports a generic trojan assessment rather than a firmly identified family. One completed sandbox run recorded offensive techniques T1055, T1485, T1486, and T1548, with process evidence involving LSASS. The executable is unsigned and has no established signer history to offset these signals. No explicit sandbox malware verdict or malicious dropped child was recorded, and the contacted IP was not covered by a saved host-reputation check, but those limitations do not outweigh the independent detections and offensive runtime indicators.
What We Detected
Twenty-three of 75 antivirus engines flagged the executable. Four high-trust products contributed detections: Microsoft reported Wacatac, Fortinet reported PossibleThreat, Symantec reported a high-confidence machine-learning attribute, and TrendMicro-HouseCall reported a generic 64-bit trojan. The labels do not converge on one named family, but the breadth and quality of detection materially reduce the likelihood of an isolated false alarm.
Threat Behavior
One completed sandbox run mapped activity to T1055 process injection, T1485 data destruction, T1486 data encrypted for impact, and T1548 privilege escalation. Saved process evidence also involved lsass.exe, which supports concern about credential-access behavior, although the available record does not prove a specific dumping method. The sample contacted 162.159.36.2 directly, but no complete host-reputation result is available because the contacted-host cross-check was not saved.
What To Do Now
Do not run the file on a production or personal system. Keep endpoint protection enabled, quarantine or remove the executable, and investigate any machine where it already ran for credential exposure, unusual child processes, injected processes, and unexpected file changes.
Where this verdict could be wrong5 caveats
- engines.tier1FamilyConsensus.strong=false, and the four high-trust detections do not agree on a named family.
- behaviour.hasMaliciousSandboxVerdict=false; the completed sandbox run did not issue an explicit malware verdict.
- droppedChildren.hasMaliciousChild=false, although all 10 inspected children have unknown verdicts rather than established clean results.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false, providing no researcher-curated corroboration.
- BitDefender, Avast, AVG, Avira, DrWeb, and Emsisoft were among the engines that did not detect the sample.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No strong tier-1 family consensus
- No explicit malicious sandbox verdict
- No inspected child was established as malicious
- No YARAify, CIRCL, or MalwareBazaar corroboration
- PE analysis found no likely packing or high-entropy code
- 23/75 antivirus detections
- Four high-trust engines flag the executable
- Unsigned Win32 executable with no signer history
- Runtime mapping to T1055 process injection
- LSASS-related process activity
- Runtime mappings to T1485 and T1486 impact techniques
Quarantine the executable and avoid launching it. If it already ran, keep security protection enabled and perform a full endpoint scan plus credential and process-injection investigation.
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
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 13MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 31filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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.
Note: Reads your Windows user-account details.
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.
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.
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
sspm_to_txt.exe
0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\sspm_to_txt.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Users\<USER>\Desktop\sspm_to_txt.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
f.dll
C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\f.dll
04Isolated runtime analysis - Written fileObserved
_tkinter.pyd
C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\_tkinter.pyd
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
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\f.dll
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\_tkinter.pyd
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\python310.dll
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\select.pyd
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl86t.dll
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\encoding
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\http1.0
- C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\msgs
- Global\SyncRootManager
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 62446bb9f9713407b041…4adc89Never scannednever seen before
- 06b96357f5dd83d0d810…0a7621Never scannednever seen before
- 14b06796f288bc6599e4…3505edNever scannednever seen before
- db85f2f94d4994283e10…51d9e9Never scannednever seen before
- fbfd065f861ec0a90dd5…af7860Never scannednever seen before
- cd2f60075064dfc2e65c…356b08Never scannednever seen before
- 1fb2d66c056f69e8bbdd…98aa2eNever scannednever seen before
- 9d2b40f0395cc5d1b4d5…4ad1b1Never scannednever seen before
- 517204ee436d08efc287…ad772cNever scannednever seen before
- 1947f8b188ab4ab6aa72…368fb7Never 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.
- 3rule hits recorded
- 23 / 75engines flagged
- 2sources 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
23 of 75 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: sspm_to_txt.exe — 0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\sspm_to_txt.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Users\<USER>\Desktop\sspm_to_txt.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: f.dll — C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\f.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _tkinter.pyd — C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\_tkinter.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved 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
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.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.
Evidence162.159.36.2
23 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
- sspm_to_txt.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 5.0 MB
- Last analyzed
- Sep 9, 2026, 10:45 PM UTC
0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5dSafety & 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 any of your files were locked or renamed, do NOT pay the ransom — payment rarely restores files. Recover them from a backup instead.
- 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 sspm_to_txt.exe a virus?
What is sspm_to_txt.exe?
How many antivirus engines detected sspm_to_txt.exe?
What should I do if I already ran sspm_to_txt.exe?
How do I remove sspm_to_txt.exe?
What kind of malware is sspm_to_txt.exe?
What is the SHA-256 hash of sspm_to_txt.exe?
How up to date is this analysis of sspm_to_txt.exe?
Community
Member reviews and reports for this exact file hash.