GridinSoft Threat Intelligence

IVMS.dll file report

Under review File reputation report
MD5 39e9c0c3d645031c9d15e430b100bc36
Latest seen 2026-02-05 23:01:38 (3 months ago)
First seen 2023-07-10 23:23:58 (2 years ago)
Size 2 MB
Publisher SPSoft
Product IVMS
Signed by SPsoft Co., Ltd.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-07-10 23:23:58 (2 years ago); latest analysis 2026-02-05 23:01:38 (3 months ago).

Publisher context

Company metadata: SPSoft. Product metadata: IVMS.

Digital signature

Signed by SPsoft Co., Ltd.. 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

IVMS.dll is a Windows file recorded in the ThreatInfo database. It is associated with IVMS. The reported company name is SPSoft. The current detection status is Undefined, based on the latest analysis from 2026-02-05 23:01:38 (3 months ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: IVMS
Company Name: SPSoft
MD5: 39e9c0c3d645031c9d15e430b100bc36
Size: 2 MB
First Published: 2023-07-10 23:23:58 (2 years ago)
Latest Published: 2026-02-05 23:01:38 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-05 23:01:38 (3 months ago)
Signed By: SPsoft Co., Ltd.
Status: Valid

The signature on IVMS.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%

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

Windows 10 71.4%
Windows 7 28.6%

The most common operating system signal for IVMS.dll is Windows 10 with 71.4% 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.

IVMS.dll is identified as pe for 32-bit 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x0014c819
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2084352

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 1558016 bytes · 74.7% of section data
MD5 0dbfc3ada3f4a79d0a5f0b0ae140779e
.rdata 350720 bytes · 16.8% of section data
MD5 443128c5eaf8b99f1b58fb8ea10e4b24
.data 21504 bytes · 1.0% of section data
MD5 c39b5339809d762f8d79ef00d0ef8613
.rsrc 14336 bytes · 0.7% of section data
MD5 b6ebeab8f2b688f5ead8a466929af179
.reloc 139776 bytes · 6.7% of section data
MD5 624f6f398c4e23e5470c6fec9c41d83c

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.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 39e9c0c3d645031c9d15e430b100bc36.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.