binkw32.dll file report

MD5 002cdf612509807b33e4ab09c686a966
Latest seen 2026-01-06 23:00:23 (4 months ago)
First seen 2017-05-27 03:07:54 (8 years ago)
Size 367 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-27 03:07:54 (8 years ago); latest analysis 2026-01-06 23:00:23 (4 months ago).

Publisher context

Company metadata: RAD Game Tools, Inc.. Product metadata: Bink and Smacker.

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.

binkw32.dll is a Windows file recorded in the ThreatInfo database. It is associated with Bink and Smacker. The reported company name is RAD Game Tools, Inc.. The current detection status is Undefined, based on the latest analysis from 2026-01-06 23:00:23 (4 months 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: Bink and Smacker
Company Name: RAD Game Tools, Inc.
MD5: 002cdf612509807b33e4ab09c686a966
Size: 367 KB
First Published: 2017-05-27 03:07:54 (8 years ago)
Latest Published: 2026-01-06 23:00:23 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-06 23:00:23 (4 months ago)
%programfiles%\qvodplayer\codecs
%programfiles%\tencent\qqplayer
%programfiles%\baofeng\encoder\codec
%appdata%\pplive\codec\1.0.0.2
%programfiles%\far_cry_in_russian_2\bin32
%programfiles%\qvodplayer
%programfiles%\tencent
%programfiles%\qvodplayer
%programfiles%\qvodplayer
%programfiles%\qvodplayer

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

81.0%
5.3%
3.2%
2.6%
1.6%
1.6%
1.1%
1.1%
0.5%
0.5%
0.5%
0.5%
0.5%

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

Windows 10 77.9%
Windows 7 16.8%
Windows 8.1 3.2%
Windows XP 1.6%
Windows 8 0.5%

The most common operating system signal for binkw32.dll is Windows 10 with 77.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.

binkw32.dll is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x30000000
Entry Address: 0x00006ab1

PE Sections:

Name Size of data MD5
.text 54784 7f5931b146c87797572d249bf434b9f3
BINK 77312 b353cd0faeea3c0cd2d0daece4f2f7e2
BINK16 6656 e95fb9e50e548f7390d29bb6c0ed9220
BINK4444 7680 114b8b3bfd027caeb152a9b2154d70c0
BINK5551 6656 7f95bff63b08cc0dd134cc3c76e3a5b9
BINK32 6656 6b3317a45f9b7ba4c62023321092f7ab
BINK32A 7680 f2f9e4c8da9860c301f61f11313e38df
BINK16X2 3584 ad02bd1ba2fd31896f1b9bc43e77b8a8
BINK32X2 3584 405c5b7ad2f5f6db1838ad24ae9474e0
BINK16MX 1024 e2f414312a7f6ebe68a467b404567618
BINK32MX 1024 c1f17f181316b82834fa5cb16eeccded
BINK16M 512 b4c9b4d7f4331ab02f0c306580308554
BINK32M 1024 d148d14435e2178cd4504b40e92806e6
BINKYUY2 512 025be532c4886b1b22b02390e4aadd46
BINKYUY2 3584 2fb150521e1a9ce7c31f6ce5f065a3ff
BINKYUY2 512 db342c40740d86199b5c4c1cc634b5a8
BINKYUY2 512 72c481a56e618c7981cabbd51fc37aa4
BINK32R 5632 d819c9ea61c20b2193457a0064fdb2d8
BINK32RA 6144 dc26195eab4ade20b1e54b978cdd743b
BINK32RX 3584 f0da84cc064542c2e07203d31f50d237
BINK24 7680 30483ef005c4d6be2e496e99aaf03207
BINK24X2 4608 35b9b5364ae0a6eee152ccbc4558544e
BINK24M 1024 bb93ab16735ebbeac01d89cc4aced61f
BINK24R 6656 8c33c21c3c2e33a6ba26f35937b5cb60
BINK24RX 4608 c7926ea27ffc0f88f5e745f37e08fae8
BINK24RM 1024 95d23863439c3ae527aba10d47854b27
BINKUYVY 512 2db773cb12da6f00fdcbb0f3f0edf4c3
BINKUYVY 512 68b20821243e8b91a5bded471d7bddf8
BINKUYVY 4096 dc33d39a0cae1b221a94e31375624246
BINKUYVY 512 2016b4c70af003cd30a8080468828cdb
BINKYV12 1024 eaaa12586820d12d502bd723b8542523
.rdata 45056 8b6ca0009d69c45a44be2b4905718d3c
.data 2560 96e5000e37961cca17e0f3f0299bc74b
BINKDATA 65024 a18666f192a335ef1d1b33c073f8b29f
.rsrc 8704 03ee5487e367143927041639d05d1b10
.reloc 21504 cbfb939a7c16bb9c70bb8fe031589d1f

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.

More information: