GridinSoft Threat Intelligence

swresample-4.dll file report

Under review File reputation report
MD5 7fb892e2ac9ff6981b6411ff1f932556
Latest seen 2025-02-17 23:00:55 (a year ago)
First seen 2025-01-11 23:05:58 (a year ago)
Size 155 KB
Publisher FFmpeg Project
Product FFmpeg
Signed by Hugh Bailey

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-01-11 23:05:58 (a year ago); latest analysis 2025-02-17 23:00:55 (a year ago).

Publisher context

Company metadata: FFmpeg Project. Product metadata: FFmpeg.

Digital signature

Signed by Hugh Bailey. 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.

File context

swresample-4.dll is a Windows file recorded in the ThreatInfo database. It is associated with FFmpeg. The reported company name is FFmpeg Project. The current detection status is Undefined, based on the latest analysis from 2025-02-17 23:00:55 (a year 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.

File Details

Product Name: FFmpeg
Company Name: FFmpeg Project
MD5: 7fb892e2ac9ff6981b6411ff1f932556
Size: 155 KB
First Published: 2025-01-11 23:05:58 (a year ago)
Latest Published: 2025-02-17 23:00:55 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-17 23:00:55 (a year ago)

Overview

Signed By: Hugh Bailey
Status: Valid

The signature on swresample-4.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.

Common Places:

%appdata%\triaox completely solutions

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

Geographic signal

Observed country distribution

ThreatInfo has seen swresample-4.dll across 3 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 33.3%
Low High activity

The strongest geographic signal for this file is United States with 33.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 100.0%

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

Analysis

swresample-4.dll is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x00001350
Image base 0x0000000180000000

PE Sections:

Sections 12
Raw data 125440

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

.text 92160 bytes · 73.5% of section data
MD5 6a3a4bad6e8fed81db714cf034676619
.data 512 bytes · 0.4% of section data
MD5 ddc09c9e90bb9438542c102300b8e6c2
.rdata 20992 bytes · 16.7% of section data
MD5 6361da6d8a18c414619dd680dddc6ce1
.pdata 2560 bytes · 2.0% of section data
MD5 5d2c771a3ae44d7f415044b84862898c
.xdata 2560 bytes · 2.0% of section data
Uncommon name
MD5 53f0d9a7460ab5c30070f3b69f7984b4
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.edata 1024 bytes · 0.8% of section data
MD5 b5321cbcdd673d8844fe6d0c1acc9da9
.idata 2560 bytes · 2.0% of section data
MD5 1cb183627992c44a69a6f758a9c2d63c
.CRT 512 bytes · 0.4% of section data
MD5 e418e905246509a669e3ea9131c7be92
.tls 512 bytes · 0.4% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1024 bytes · 0.8% of section data
MD5 3011b0b5b92bbbf5bcfab0d50d89074f
.reloc 1024 bytes · 0.8% of section data
MD5 e8e91cfd7b2cb1dcafa353361b8fb467

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 7fb892e2ac9ff6981b6411ff1f932556.
  • 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.