SoundFlowPicker.exe threat report

MD5 2ea6cf2ef767c1032d676103f815e36a
Latest seen 2021-11-09 21:46:04 (4 years ago)
First seen 2021-11-09 21:46:04 (4 years ago)
Size 960 KB
Publisher SWE Sven Ritter
Product SpeedCommander

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Sabsik. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Sabsik
Recommended action
Scan and remove
Last analysis
2021-11-09 21:46:04 (4 years ago)
File hash
2ea6cf2ef767c1032d676103f815e36a
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Sabsik.

Timeline

First seen 2021-11-09 21:46:04 (4 years ago); latest analysis 2021-11-09 21:46:04 (4 years ago).

Publisher context

Company metadata: SWE Sven Ritter. Product metadata: SpeedCommander.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

SoundFlowPicker.exe is a Windows file recorded in the ThreatInfo database. It is associated with SpeedCommander. The reported company name is SWE Sven Ritter. The current detection status is Trojan.Sabsik, based on the latest analysis from 2021-11-09 21:46:04 (4 years ago).

If SoundFlowPicker.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Sabsik.

Product Name: SpeedCommander
Company Name: SWE Sven Ritter
MD5: 2ea6cf2ef767c1032d676103f815e36a
Size: 960 KB
First Published: 2021-11-09 21:46:04 (4 years ago)
Latest Published: 2021-11-09 21:46:04 (4 years ago)
Status: Trojan.Sabsik (on last analysis)
Analysis Date: 2021-11-09 21:46:04 (4 years ago)
SoundFlowPicker.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%commonappdata%

ThreatInfo has observed SoundFlowPicker.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.

100.0%

The strongest geographic signal for this file is Indonesia with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for SoundFlowPicker.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.

SoundFlowPicker.exe is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x00069a20

PE Sections:

Name Size of data MD5
.text 434176 af7b0a8727fa3adcd5b94798b106256e
.rdata 8192 fe917427b0f67d89b2346f7e2f8ce4a3
.data 4096 590b62aa5a6e956414d1680cd9d6dfae
.data1 4096 feffe703e74573f5e88b8b266e6b76ec
.sif 8192 b49148d751bbe8236885c43464d49eb3
.rsrc 520192 b14d48d903029177ad9f0c7777e2ab34

PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.

More information: