GridinSoft Threat Intelligence

libsodium.dll file report

Under review File reputation report
MD5 81715bf40e32a1fadc522159dea716f6
Latest seen 2023-10-18 23:12:32 (2 years ago)
First seen 2023-10-18 23:12:32 (2 years ago)
Size 543 KB
Product libsodium

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-10-18 23:12:32 (2 years ago); latest analysis 2023-10-18 23:12:32 (2 years 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 2023-10-18 23:12:32 (2 years 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: 81715bf40e32a1fadc522159dea716f6
Size: 543 KB
First Published: 2023-10-18 23:12:32 (2 years ago)
Latest Published: 2023-10-18 23:12:32 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-10-18 23:12:32 (2 years 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 0x00063ecd
Image base 0x10000000

PE Sections:

Sections 5
Raw data 541696

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

.text 449024 bytes · 82.9% of section data
MD5 f4b7685f35c62a802445384423f4908c
.rdata 81920 bytes · 15.1% of section data
MD5 5ecda2302dbb178ff09f34c04dd07441
.data 3072 bytes · 0.6% of section data
MD5 cedc87e994dbe7cd86473162a92391eb
.rsrc 1536 bytes · 0.3% of section data
MD5 fee34c4cd973f9dcd050f7c8dd95d61f
.reloc 6144 bytes · 1.1% of section data
MD5 daf6adb78a3ab4337a012cfbacb33918

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 81715bf40e32a1fadc522159dea716f6.
  • 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.