MalwareTips

File scan report

Scan another file

Verdict Malicious

Analyzed , 1 month ago

Is sspm_to_txt.exe safe? No, we rate this exact file malicious.

The executable is flagged by 23 of the 70 antivirus engines that checked it, including four major antivirus engines, and it lacks a verified signature.

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Don't run this file

If you already ran it, follow the steps below.

What to do now4 steps

This file is harmful. Don't run it, and remove it.

If you haven't run it

  1. Don't run this file. Delete it, then empty the Recycle Bin.

If you already ran it

  1. Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.

  2. If you typed passwords on the device after running it, change them from another device you trust.

  3. If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.

If you already ran it, do these in order.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

sspm_to_txt.exe: Malicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

23 of 70 flagged

  • Flagged 23
  • No detection 47
  • No result 5
Filesspm_to_txt.exe5.2 MBSHA-256 0ada0cf0cc90…1f9e5d
  • Code signing Unsigned
  • Test run Completed
  • First seen 5mo ago
23 of the 70 antivirus engines that checked it flag it, including Microsoft and Symantec (Norton).

Chapter 02

Why we think so

5 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The detection volume is substantial: 23 of the 70 antivirus engines that checked it flag the executable, with Microsoft, Fortinet, Symantec, and TrendMicro-HouseCall contributing four major 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. The executable is unsigned and has no established signer history to offset these signals. No explicit sandbox malware verdict or malicious file it created 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.

Where this verdict could be wrong5 caveats
  • Major antivirus engines do not agree on one malware family, and the four major detections do not agree on a named family.
  • No sandbox returned a malicious verdict; the completed sandbox run did not issue an explicit malware verdict.
  • No dropped file is known to be malicious, although all 10 inspected children have unknown verdicts rather than established clean results.
  • No community YARA rule matched and the hash is not in the known-software reference database, 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.

6 sources checked · 5 complete · 1 not needed or not applicable. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 13sandbox rule tags
  • 4spawned processes
  • 0network contacts
  • 31filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Checked whether it was running on a test computer.

  • Note: Read the user name of the test computer.

  • Note: Read basic details of the test computer, such as its Windows version.

  • Note: Looked through folders on the test computer (most installers do this).

  • Note: Loaded extra code modules while running.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Threat context

How trojans work

A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, 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.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 5: FileSeen in the test run

      sspm_to_txt.exe

      0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5d

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 5: ProcessSeen in the test run

      sspm_to_txt.exe

      "C:\Users\<USER>\Desktop\sspm_to_txt.exe"

      Test run
    2. Evidence 3 of 5: ProcessSeen in the test run

      sspm_to_txt.exe

      C:\Users\<USER>\Desktop\sspm_to_txt.exe

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 5: Written fileSeen in the test run

      f.dll

      C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\f.dll

      Test run
    2. Evidence 5 of 5: Written fileSeen in the test run

      _tkinter.pyd

      C:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\_tkinter.pyd

      Test run
    3. +1 more recorded observation

5 facts from the test run. See the full activity list.

Chapter 04

Technical details

23 of the 70 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteRisk signal: 23 of 70 engines flagged it · 5 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 23

  • Fortinet (major engine)W32/PossibleThreat
  • Microsoft (major engine)Trojan:Win32/Wacatac.B!ml
  • Symantec (major engine)ML.Attribute.HighConfidence
  • TrellixENS (major engine)Artemis!F880367D314D
  • TrendMicro-HouseCall (major engine)Trojan.Win64.Gen.TL0101E226YU
  • APEXMalicious
  • BkavW32.Malware.1CF4FAB4
  • CrowdStrikewin/malicious_confidence_70% (W)
15 more in the full engine list

File fingerprint

Last analyzed
Sep 9, 2026, 10:45 PM UTC
SHA-256
0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5d
SHA-1
bd743aa6ff8abf816b1e0e7d0d99616acdd904d9
MD5
f880367d314dfae1faa011b1e6f65fa5

About this file

sspm_to_txt.exe is a Win32 EXE file of 5.2 MB.

Type and size
Win32 EXE · 5.2 MB
Signer
UnsignedNo code signature.
First seen
Apr 30, 2026On VirusTotal.
Submitted by
2 distinct sourcesRarely seen: few people have submitted this exact file.
Packer
None detected
Entropy
6.04 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 8 questions people ask most about this file.

Is sspm_to_txt.exe a virus?
Yes. This copy of sspm_to_txt.exe (SHA-256 0ada0cf0…9e5d) is malicious. Other files with the same name can be different, so check the hash. Don't run it. Delete it, then empty the Recycle Bin. 23 of the 70 antivirus engines that checked it flag it. Antivirus engines classify it as a trojan: malware disguised as something harmless so that you run it. If you've already run it, see the steps below.
What is sspm_to_txt.exe?
sspm_to_txt.exe is a Windows program, about 5.2 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Apr 30, 2026.
How many antivirus engines detected sspm_to_txt.exe?
23 of the 70 antivirus engines that checked it flag sspm_to_txt.exe, including Microsoft and Symantec (Norton). We weigh which engines flagged it and what else the scan found, not just the count. The rating comes from all the evidence together, not from this count alone.
What should I do if I already ran sspm_to_txt.exe?
Act quickly. 1) Disconnect the device from the internet. 2) Run a full scan with your antivirus and let it remove what it finds. 3) Change your important passwords from another device you trust, starting with email and banking, and turn on two-step verification. 4) If you bank or shop on this device, watch your accounts and tell your bank about payments you don't recognise. 5) If the scan keeps finding it, back up your personal files and reinstall Windows.
How do I remove sspm_to_txt.exe?
To remove sspm_to_txt.exe: 1) run a full scan with your antivirus and let it remove what it finds. 2) Delete it, then empty the Recycle Bin. 3) Check Settings > Apps, your browser extensions, startup apps (Task Manager > Startup apps) and scheduled tasks for anything you don't recognise. 4) Restart and scan again. If it keeps coming back, scan from Safe Mode with Networking, or back up your files and reinstall Windows.
What kind of malware is sspm_to_txt.exe?
Antivirus engines classify sspm_to_txt.exe as a trojan: malware disguised as something harmless so that you run it.
What is the SHA-256 hash of sspm_to_txt.exe?
The SHA-256 fingerprint of sspm_to_txt.exe is 0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5d, and its MD5 is f880367d314dfae1faa011b1e6f65fa5. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of sspm_to_txt.exe?
This report reflects the scan on Sep 9, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.