GridinSoft Threat Intelligence
swscale-lav-4.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-08-22 12:03:38 (8 years ago); latest analysis 2022-08-25 23:14:25 (3 years ago).
Company metadata: FFmpeg Project. Product metadata: FFmpeg.
Signed by Hendrik Leppkes. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
swscale-lav-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 2022-08-25 23:14:25 (3 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.
File Details
| Product Name: | FFmpeg |
| Company Name: | FFmpeg Project |
| MD5: | 65a7f29cce0a54d2c609e2bdb3e7a4cf |
| Size: | 527 KB |
| First Published: | 2017-08-22 12:03:38 (8 years ago) |
| Latest Published: | 2022-08-25 23:14:25 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-08-25 23:14:25 (3 years ago) |
Overview
| Signed By: | Hendrik Leppkes |
| Status: | Valid |
The signature on swscale-lav-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:
| %programfiles%\splitcam\dsfilters\lavfilters |
| %programfiles%\splitcam\dsfilters |
| %programfiles%\frol9999\player\filters |
| %programfiles%\software\note5\note5_5.1.4.36469\main |
ThreatInfo has observed swscale-lav-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 swscale-lav-4.dll across 20 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Spain with 22.8% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for swscale-lav-4.dll is Windows 10 with 67.9% 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
swscale-lav-4.dll is identified as pe for 32-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
dbfd0cbce72fca0464432ad86921b18e
b65782da67ada0d97e50169d57f5fabd
d6c8e53bf124a4abab661b8d0c64c86e
52b569b74c67eabc7cfdb39564f42c1c
00000000000000000000000000000000
6b2ba3d27392ff16db2cf550f2ae6e8b
d79b9e1c04cf28b720a2076b8458118f
5c91dba83ce6491a3a151950f91dfe9b
9cb32661a66c0fdbe6ce2103c8e39ad1
bd5d4e779b5d6677b640a5c31387fcbc
5bdad0facbd08cd2d4294b4b5f98c7f2
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.