File scan report
Verdict Suspicious
Is wooferbot.
Three of the 68 antivirus engines that checked it raised generic concerns, but major antivirus engines and the combined sandbox result did not corroborate ransomware or process injection.
Why Suspicious? 3 antivirus engines flag it, but no major engine agrees and one of our detection rules matched it.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 68 flagged
- Flagged 3
- No detection 65
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 4y ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 3 of the 68 antivirus engines that checked it flagged this unsigned PyInstaller executable, and no major antivirus engines identified malware. The combined sandbox verdict was clean, with no named injection target or other high-risk technique, but the detections and limited prevalence justify caution until the file's source is verified.
The engine evidence is limited to three generic detections, with no major detection or malware-family consensus. Although one engine described ransomware-like behavior, the sandbox runs recorded neither file encryption nor a genuine ransom-note pattern; the matched README files were extracted within a PyInstaller temporary directory. The mapping had no named injection target and therefore does not establish process injection. The sole observed domain was fully checked against the saved host-reputation data and had no malicious or suspicious result. Because the executable is unsigned, infrequently submitted, and unavailable for our static analysis, the remaining uncertainty prevents treating the weak detections as conclusively false positives.
What We Detected
Three of the 68 antivirus engines that checked it flagged the executable. Skyhigh reported ransomware-like behavior, while APEX and Bkav supplied generic malware labels; none of the 18 major antivirus engines that reported a result flagged it, and no malware family was identified.
Threat Behavior
The combined sandbox verdict was clean. No named process-injection target, file-encryption activity, persistence indicator, malicious dropped file, or other high-risk technique was recorded. A behavior rule matched README filenames extracted under a PyInstaller temporary directory, but that context does not demonstrate ransom-note creation. The sole observed domain was covered by the saved reputation check and had no malicious or suspicious result.
What To Do Now
Confirm that the file came directly from its expected developer or distribution channel before running it. Keep security software enabled and, if the source cannot be verified, avoid execution or test it only in an isolated environment.
Where this verdict could be wrong3 caveats
- Skyhigh's ransomware-like behavior label and the two generic detections are adverse signals, even though no major antivirus engines corroborated them.
- The executable is unsigned and has only four distinct submitters, so it lacks a verified publisher or broad-distribution anchor.
- Our static analysis was unavailable because the bytes were not uploaded, leaving the packaged contents unexamined by that check.
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 major antivirus engines flagged the file.
- The combined sandbox verdict was clean and recorded no named injection target or file-encryption activity.
- The saved host-reputation check covered the sole observed domain and found no malicious or suspicious result.
- No malicious file it created or external-intelligence match was found.
- The apparent packing was identified as PyInstaller, and the executable code did not have unusually high entropy.
- Three antivirus engines raised generic or ransomware-like concerns.
- The executable is unsigned, so its publisher cannot be authenticated.
- Only four distinct sources submitted this file, providing limited prevalence evidence.
- Our static analysis was unavailable, so the packaged contents were not examined by that check.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 6 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 6isolated sandbox runs
- 7sandbox rule tags
- 2spawned processes
- 1network contact
- 15filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a 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.
Note: Connected to 1 server during the test run.
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: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 6: FileSeen in the test run
wooferbot.exe
0859d2d03c97405dc3a477fd68c74278c86513e25539a8a66b6256fdaf64c1d8
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
wooferbot.exe
Test run - Evidence 3 of 6: ProcessSeen in the test run
cmd.exe
C:\Windows\System32\cmd.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
README.txt
C:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\Icons\README.txt
Test run - Evidence 5 of 6: Written fileSeen in the test run
README.txt
C:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\README.txt
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
arc.msn.com
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 6 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
7MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1055· Process injection
- T1059· Runs commands
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1497.001· Sandbox evasion
- T1574.002· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
wooferbot.exe%SAMPLEPATH%\wooferbot.execmd.exeC:\Windows\System32\cmd.exe
Network contacts
11 host, listed as 1 domain. Links show the host and path only.
- Domain
arc.msn.com
Files
15Files the file created, changed or deleted.
- Written
C:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\Icons\README.txt - Written
C:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\README.txt - Written
C:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\idle_test\README.txt - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Antarctica\Rothera - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Antarctica\South_Pole - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Antarctica\Syowa
Show all 15 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Antarctica\Troll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Antarctica\Vostok - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Arctic\Longyearbyen - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Asia\Aden - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Asia\Almaty - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Asia\Amman - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Asia\Anadyr - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Asia\Aqtau - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI22442\tcl\tzdata\Asia\Aqtobe
Registry and auto-start
1Settings the file changed, including ways to start again after a restart.
- Set
HKLM\SOFTWARE\Microsoft\Windows Media Player NSS\3.0\Servers\A70D59A1-8EAD-4F40-AAAB-FBFC460800A4\FriendlyName
Chapter 04
Technical details
3 of the 68 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- APEXMalicious
- BkavW64.AIDetectMalware
- SkyhighBehavesLike.Win64.Ransom.rc
File fingerprint
- Last analyzed
- Nov 9, 2026, 3:39 AM UTC
- SHA-256
0859d2d03c97405dc3a477fd68c74278c86513e25539a8a66b6256fdaf64c1d8- SHA-1
797eec3d9f2de9fc37299ccd6eeea88caaae5d0f- MD5
27b4d22e44d403f5153b4459e67fd4f7
About this file
wooferbot.exe is a Win32 EXE file of 12.9 MB.
- Type and size
- Win32 EXE · 12.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Mar 24, 2022On VirusTotal.
- Submitted by
- 4 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- PyInstaller (DetectItEasy packer)Packing hides code; legitimate installers use it too.
- Entropy
- 5.94 of 8
First scanned
Antivirus consensus
3 of 68 engines flagged this file
5 of the 73 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-235 engines1flagged
- Low-trust15 engines2flagged
View all 73 engine results
- APEXMalicious: Malicious
- BkavMalicious: W64.AIDetectMalware
- SkyhighMalicious: BehavesLike.Win64.Ransom.rc
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BaiduClean
- BitDefenderClean
- BitDefenderFalxNo result
- BitDefenderThetaClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeNo result
- CybereasonClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MAXClean
- MaxSecureClean
- McAfeeClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
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.
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.
EvidenceT1055 (sandbox MITRE mapping)Sample wrote 3 files matching ransomware-note patterns (readme / HOW_TO_DECRYPT / .locked / .encrypted). Multi-directory note drops are the hallmark of file-encryption ransomware.
EvidenceC:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\Icons\README.txt · C:\Users\user\AppData\Local\Temp\_MEI47882\idlelib\README.txtUnsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidencearc.msn.com
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is wooferbot.exe safe, or is it malware?
What is wooferbot.exe?
How many antivirus engines detected wooferbot.exe?
What should I do if I already ran wooferbot.exe?
What is the SHA-256 hash of wooferbot.exe?
How up to date is this analysis of wooferbot.exe?
Community
Member reviews and reports for this exact file hash.