SpaceBlender.vst3 threat report

MD5 6311b3b62b3c38a2e93fdd66f36fbc0d
Latest seen 2025-05-05 23:00:25 (a year ago)
First seen 2025-05-05 23:00:24 (a year ago)
Size 56 MB
Publisher SoundToys
Product SpaceBlender
Signed by Soundtoys Inc.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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.Heur!
Recommended action
Scan and remove
Last analysis
2025-05-05 23:00:25 (a year ago)
File hash
6311b3b62b3c38a2e93fdd66f36fbc0d
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2025-05-05 23:00:24 (a year ago); latest analysis 2025-05-05 23:00:25 (a year ago).

Publisher context

Company metadata: SoundToys. Product metadata: SpaceBlender.

Digital signature

Signed by Soundtoys Inc.. The signature is reported as valid, but signed files can still be bundled or abused.

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.

SpaceBlender.vst3 is a Windows file recorded in the ThreatInfo database. It is associated with SpaceBlender. The reported company name is SoundToys. The current detection status is Trojan.Heur!, based on the latest analysis from 2025-05-05 23:00:25 (a year ago).

If SpaceBlender.vst3 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.Heur!.

Product Name: SpaceBlender
Company Name: SoundToys
MD5: 6311b3b62b3c38a2e93fdd66f36fbc0d
Size: 56 MB
First Published: 2025-05-05 23:00:24 (a year ago)
Latest Published: 2025-05-05 23:00:25 (a year ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2025-05-05 23:00:25 (a year ago)
SpaceBlender.vst3 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.

Signed By: Soundtoys Inc.
Status: Valid

The signature on SpaceBlender.vst3 is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%commondir%\vst3
%commondir%\vst3

ThreatInfo has observed SpaceBlender.vst3 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.

50.0%
50.0%

The strongest geographic signal for this file is Canada with 50.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 SpaceBlender.vst3 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.

SpaceBlender.vst3 is identified as pe for 64 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: 64
Image Base: 0x0000000180000000
Entry Address: 0x07ff2e90

PE Sections:

Name Size of data MD5
.text 11118080 fb9fee95bc806a22f41d1dd513fa318f
.rdata 1528832 83f4bcff2a20970378905c836b75b54a
.data 7579136 4966bc0c5fb21a9ba70905ab787a64a5
.pdata 199168 a102891692f13d9d2bd744f983e0b13a
.mfrt 512 912e20b1c98b0eed0cc4a6ad272540df
_RDATA 512 9cb14b69d7b0d91a9a2eade58530d715
.rsrc 29131776 325829de4514a8b86cefdf20d613496f
.oldrel 79360 aabe9cd139cc7e097d284fa105fa90f5
.reloc64 306176 022d904829fc0cb002f420228cfe99f8
.text001 4608 00da7fd44650201c370430a9e753950a
.rdata01 3072 18db09f2ca3b685b5391fe7d8b581d8b
.data001 512 c61ec110f9fc0f974106e9563d3849d3
.pdata01 512 6904a603825ec34c5ba11e7ed38070ef
.rsrc001 1536 847d5a946f9211e1fcbc20f60e572c50
.reloc 512 cb952a46d6d777e1d0acdeec4cc95797
.proxy 1748480 96a466cf5d8bd2572a029f489f38bd63
.guard 8000000 e62f08e3032c1b55a5606b226a26fedc

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: