GridinSoft Threat Intelligence

libsodium.dll file report

Under review File reputation report
MD5 4f28dccb284762552b4a6212ec427a6f
Latest seen 2026-05-04 23:00:43 (a week ago)
First seen 2025-06-16 23:01:16 (11 months ago)
Size 480 KB
Product libsodium

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-06-16 23:01:16 (11 months ago); latest analysis 2026-05-04 23:00:43 (a week ago).

Publisher context

Product metadata: libsodium.

Digital signature

Signed by INNOVATIVE CONNECTING PTE. LIMITED. 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.

libsodium.dll is a Windows file recorded in the ThreatInfo database. It is associated with libsodium. The current detection status is Undefined, based on the latest analysis from 2026-05-04 23:00:43 (a week 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: libsodium
MD5: 4f28dccb284762552b4a6212ec427a6f
Size: 480 KB
First Published: 2025-06-16 23:01:16 (11 months ago)
Latest Published: 2026-05-04 23:00:43 (a week ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-05-04 23:00:43 (a week ago)
Signed By: INNOVATIVE CONNECTING PTE. LIMITED
Status: Valid

The signature on libsodium.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%\turbovpn

ThreatInfo has observed libsodium.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 100.0%

The most common operating system signal for libsodium.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.

libsodium.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 0x000642af
Image base 0x10000000

PE Sections:

Sections 5
Raw data 477696

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

.text 409088 bytes · 85.6% of section data
MD5 178b759ee1e17ec9690f7527a714d8cc
.rdata 62464 bytes · 13.1% of section data
MD5 ac130fef904ade1a4374182d9a24cb11
.data 1024 bytes · 0.2% of section data
MD5 d286209be425fdd38e565d2400d10b7f
.rsrc 1536 bytes · 0.3% of section data
MD5 6f19bf598136f6702632999e9a74724f
.reloc 3584 bytes · 0.8% of section data
MD5 61283e0393ec5f90c7d7d39e51a4ce20

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 4f28dccb284762552b4a6212ec427a6f.
  • 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.