GridinSoft Threat Intelligence
filavutd.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-05-21 06:06:09 (9 years ago); latest analysis 2022-08-21 23:33:05 (3 years ago).
Company metadata: Filseclab Corporation. Product metadata: Filseclab Virut Removal Tool.
Signed by Filseclab Corporation. 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
filavutd.dll is a Windows file recorded in the ThreatInfo database. It is associated with Filseclab Virut Removal Tool. The reported company name is Filseclab Corporation. The current detection status is Undefined, based on the latest analysis from 2022-08-21 23:33:05 (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: | Filseclab Virut Removal Tool |
| Company Name: | Filseclab Corporation |
| MD5: | c29cd10cc642f7a24c107140c39f4c23 |
| Size: | 108 KB |
| First Published: | 2017-05-21 06:06:09 (9 years ago) |
| Latest Published: | 2022-08-21 23:33:05 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2022-08-21 23:33:05 (3 years ago) |
Overview
| Signed By: | Filseclab Corporation |
| Status: | Valid |
The signature on filavutd.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%\elex-tech\yac\tws\plugins |
| %programfiles%\isafe\tws\plugins |
| %sysdrive%\archivos de programa\elex-tech\yac\tws\plugins |
| %programfiles%\elex-tech\yac\tws |
| %sysdrive%\archivos de programa\elex-tech\yac\tws |
| %sysdrive%\archivos de programa\isafe\tws |
| %programfiles%\isafe\tws |
ThreatInfo has observed filavutd.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 filavutd.dll across 35 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Vietnam with 23.0% 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 filavutd.dll is Windows 7 with 62.7% 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
filavutd.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d8246112316e5dbe16cf7834feed075a
3481d85c3a7db574deaaccc92084ca16
5378a30ab51e1b2d085a18547b0d45d1
1191f4ca7ac4cb07f745bb73439d975c
5bd4b36f671a812bf5d1a419346050bc
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.