SpaceBlender.dll threat report

MD5 dd171e4bf156beaaceef547242415d52
Latest seen 2025-05-05 23:00:25 (a year ago)
First seen 2025-05-05 23:00:25 (a year ago)
Size 57 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
dd171e4bf156beaaceef547242415d52
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:25 (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.dll 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.dll 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: dd171e4bf156beaaceef547242415d52
Size: 57 MB
First Published: 2025-05-05 23:00:25 (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.dll 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.dll 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.

%programfiles%\vstplugins

ThreatInfo has observed SpaceBlender.dll 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 Italy 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 SpaceBlender.dll 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.dll 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: 0x080e6e90

PE Sections:

Name Size of data MD5
.text 11294208 53686a87780d90e01b5fa1da5de7bc7f
.rdata 1517056 026f1b0eccce3d9104086c8dac157962
.data 7575040 16135592e082e60ccb2e85d37875093d
.pdata 198144 ff15f7fc4ec9fe8aec2139b39623f14d
.mfrt 512 912e20b1c98b0eed0cc4a6ad272540df
_RDATA 512 3f294164962d61ee19682f7f703fb2e5
.rsrc 29131776 119277ac6ed8ea270f81dbcfef1b8cf2
.oldrel 78336 b0e87e14074341e2eef91c06bf8e538c
.reloc64 301568 178cecbc8968e56a9c212a323a89310d
.text001 4608 00da7fd44650201c370430a9e753950a
.rdata01 3072 2cea49c0f6a435e5427d1dd727519bad
.data001 512 0d73335732cae102e1fabfd8c1bb5fee
.pdata01 512 6904a603825ec34c5ba11e7ed38070ef
.rsrc001 1536 389cdfbf0b20c4a8e1ddd24f2948622b
.reloc 512 fab953cd7f900b3c371e7795e148aa4f
.proxy 1748480 96a466cf5d8bd2572a029f489f38bd63
.guard 7999488 022a9c85bd94c25ca8b409f4e5c63594

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: