File scan report

Verdict Malicious

Analyzed Sep 9, 20261 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

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

If you already ran it

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.
If you typed passwords on the device after running it, change them from another device you trust.
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

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.

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

Input file
The submitted object
1
1. Evidence 1 of 5: FileSeen in the test run
  sspm_to_txt.exe
  0ada0cf0cc90c16bcb1e70ebb422cdb951738276abfe9b3c78b09a370d1f9e5d
  Uploaded file
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
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.

Runtime behaviour

What this file did when executed

This file was run in a sandbox and its runtime behaviour was observed.

Techniques observed in the sandbox

13

MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.

T1027· Obfuscated code
T1027.002· Obfuscated code
T1033· Reads user info
T1036
T1055· Process injection
T1059· Runs commands
T1082· System recon
T1083· Scans your files
T1129· Loads modules
T1485
T1486· File encryption
T1497· Sandbox evasion
T1548

Observed activity

Processes started

4

Programs the file ran, with their command lines.

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

Files

30

Files the file created, changed or deleted.

WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\f.dll
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\_tkinter.pyd
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\python310.dll
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\select.pyd
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl86t.dll
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tk86t.dll

Show all 30 entries

WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\unicodedata.pyd
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\vcruntime140.dll
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\auto.tcl
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\clock.tcl
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\history.tcl
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\init.tcl
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\package.tcl
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\parray.tcl
WrittenC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\safe.tcl
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\encoding
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\http1.0
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\msgs
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\opt0.4
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\Africa
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\America
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\America\Argentina
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\America\Indiana
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\America\Kentucky
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\America\North_Dakota
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\Antarctica
DeletedC:\Users\<USER>\AppData\Local\Temp\onefile_5896_134220872339559298\tcl\tzdata\Arctic

Mutexes

1

Named locks a program uses so only one copy runs; malware families often reuse them.

Global\SyncRootManager

Sandbox background — not the file

8

The analysis machine's own processes and connections, recorded in every run.

VM processExplorer.EXEC:\Windows\Explorer.EXE
VM processservices.exeC:\Windows\system32\services.exe
VM processsvchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p
VM processsvchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup
VM processsvchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc
VM processlsass.exeC:\Windows\system32\lsass.exe

Show all 8 entries

VM processsvchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
VM host162.159.36.2

Dropped payload

Files this sample writes at runtime

This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.

10 not checked

62446bb9f9713407b041…4adc89Not checked
no saved verdict
06b96357f5dd83d0d810…0a7621Not checked
no saved verdict
14b06796f288bc6599e4…3505edNot checked
no saved verdict
db85f2f94d4994283e10…51d9e9Not checked
no saved verdict
fbfd065f861ec0a90dd5…af7860Not checked
no saved verdict
cd2f60075064dfc2e65c…356b08Not checked
no saved verdict
1fb2d66c056f69e8bbdd…98aa2eNot checked
no saved verdict
9d2b40f0395cc5d1b4d5…4ad1b1Not checked
no saved verdict
517204ee436d08efc287…ad772cNot checked
no saved verdict
1947f8b188ab4ab6aa72…368fb7Not checked
no saved verdict

Chapter 04

Technical details

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

SourceStatusResultChecked

Antivirus enginesVirusTotal · 75 enginesComplete23 of 70 engines flagged it · 5 gave no result DetailsJun 28, 2026

Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded DetailsSep 9, 2026

Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to check

Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule DetailsSep 9, 2026

Malware sample databaseabuse.ch MalwareBazaarCompleteNot listedSep 9, 2026

Known-software referenceCIRCL hashlookupCompleteNo matchSep 9, 2026

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 Sep 9, 2026

Antivirus consensus

23 of 70 engines flagged this file

23 malicious0 suspicious47 not flagged5 no result

5 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.

The 23 detections come from 22 independent scan engines: several vendors license the same engine, so their results are one vote.

Tier-117 engines
5flagged
Tier-236 engines
10flagged
Low-trust17 engines
8flagged

View all 75 engine results

APEXMalicious: Malicious
BkavMalicious: W32.Malware.1CF4FAB4
CrowdStrikeMalicious: win/malicious_confidence_70% (W)
CTXMalicious: exe.trojan.generic
CynetMalicious: Malicious (score: 100)
DeepInstinctMalicious: MALICIOUS
ElasticMalicious: malicious (high confidence)
FortinetMalicious: W32/PossibleThreat
GoogleMalicious: Detected
GridinsoftMalicious: Trojan.Win64.Agent.oa!s1
JiangminMalicious: Trojan.Redcap.de
LionicMalicious: Trojan.Win32.Generic.4!c
MaxSecureMalicious: Trojan.Malware.324995110.susgen
McAfeeDMalicious: ti!0ADA0CF0CC90
MicrosoftMalicious: Trojan:Win32/Wacatac.B!ml
PaloaltoMalicious: generic.ml
PandaMalicious: Trj/GdSda.A
SentinelOneMalicious: Static AI - Suspicious PE
SymantecMalicious: ML.Attribute.HighConfidence
TrapmineMalicious: malicious.moderate.ml.score
TrellixENSMalicious: Artemis!F880367D314D
TrendMicro-HouseCallMalicious: Trojan.Win64.Gen.TL0101E226YU
VaristMalicious: W64/ABTrojan.JBQD-9201
AcronisClean
AhnLab-V3Clean
AlibabaClean
alibabacloudClean
ALYacClean
Antiy-AVLClean
ArcabitClean
AvastClean
Avast-MobileNo result
AVGClean
AviraClean
BitDefenderClean
BitDefenderFalxNo result
CAT-QuickHealClean
ClamAVClean
CMCClean
CylanceClean
DrWebClean
EmsisoftClean
ESET-NOD32Clean
F-SecureClean
GDataClean
huorongClean
IkarusNo result
K7AntiVirusClean
K7GWClean
KasperskyClean
KingsoftClean
MalwarebytesClean
MicroWorld-eScanClean
NANO-AntivirusClean
RisingClean
SangforClean
SkyhighClean
SophosClean
SUPERAntiSpywareClean
SymantecMobileInsightNo result
TACHYONClean
tehtrisClean
TencentClean
TrendMicroClean
TrustlookNo result
VBA32Clean
VIPREClean
VirITClean
ViRobotClean
WebrootClean
XcitiumClean
YandexClean
ZillyaClean
ZoneAlarmClean
ZonerClean

Rule-based evidence

Signatures and behavior heuristics

Low-severity pattern matches — worth noting but not on their own cause for alarm.

1 heuristic

MITRE ATT&CK profile

Defense evasion× 1

Behavior heuristics

Deterministic patterns derived from scan data and observed runtime behavior

ProcessInjection
T1055
low
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
Evidence
T1055 (sandbox MITRE mapping)

PE forensics

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.

ent 6.04Unpacked

Section entropy10 sections

.text

6.32

.data

1.34

.rdata

5.22

.eh_fram

0.00

.pdata

4.97

.xdata

4.48

.bss

0.00

.idata

4.33

.CRT

0.29

.tls

0.00

0.0Packed threshold 7.28.0

Prevalence

How widely this file has been seen

Rarely uploaded, and first seen more than two weeks ago. Often niche legitimate software or internal tooling; not a strong malware signal on its own.

Rare & old

Unique uploaders

2

Very few people have ever uploaded this — rare.

Total submissions

2

Includes repeat uploads by the same source.

First seen

6mo ago

Apr 30, 2026

Prevalence quadrant

Rare · New

Needs evidence-led scrutiny

Common · New

Just-released software

here

Rare · Old

Niche or internal tooling

Common · Old

Often established software

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.

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

Why we think so

The reasoning behind this verdict

What We Detected

Threat Behavior

What To Do Now

What it did in our test

Test run summary

What the test run showed

Confirmed in the test run

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

Threat context

What happened in the test

Input file

Processes

Files

What this file did when executed

Techniques observed in the sandbox

Observed activity

Processes started

Files

Mutexes

Sandbox background — not the file

Files this sample writes at runtime

Technical details

Every check behind this verdict

Engines that flagged it 23

File fingerprint

About this file

23 of 70 engines flagged this file

Signatures and behavior heuristics

Section entropy & packers

How widely this file has been seen

Questions & answers

Community

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

What We Detected

Threat Behavior

What To Do Now

Test run summary

What the test run showed

Confirmed in the test run

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

Threat context

What happened in the test

Input file

Processes

Files

Techniques observed in the sandbox

Observed activity

Processes started

Files

Mutexes

Sandbox background — not the file

Engines that flagged it 23

File fingerprint

About this file

Related file reports