Launcher (1).dll file report

MD5 8122235496491f6e20525c426d2a47e3
Latest seen 2025-05-06 23:02:04 (a year ago)
First seen 2017-05-21 22:06:17 (8 years ago)
Size 1 MB
Publisher SweetLabs, Inc.
Product Pokki
Signed by Pokki

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 22:06:17 (8 years ago); latest analysis 2025-05-06 23:02:04 (a year ago).

Publisher context

Company metadata: SweetLabs, Inc.. Product metadata: Pokki.

Digital signature

Signed by Pokki. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

Launcher (1).dll is a Windows file recorded in the ThreatInfo database. It is associated with Pokki. The reported company name is SweetLabs, Inc.. The current detection status is Undefined, based on the latest analysis from 2025-05-06 23:02:04 (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.

Product Name: Pokki
Company Name: SweetLabs, Inc.
MD5: 8122235496491f6e20525c426d2a47e3
Size: 1 MB
First Published: 2017-05-21 22:06:17 (8 years ago)
Latest Published: 2025-05-06 23:02:04 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-05-06 23:02:04 (a year ago)
Signed By: Pokki
Status: Valid

The signature on Launcher (1).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.

%localappdata%\pokki\engine
%appdata%\zhp\quarantine\pokki\pokki\engine
%temp%\nsp7e8a.tmp
%temp%\nsv47a8.tmp
%sysdrive%\adwcleaner\quarantine\files\rsotlyhxseehpekdwtsolqxpayvwrbtx\engine
%sysdrive%\adwcleaner\quarantine\files\qtvvoantewfespnpphfxtqfgvkpxosea\engine
%sysdrive%\adwcleaner\quarantine\files\zkkcohtexeglkekgnljsecpaksxwzkpx\engine
%sysdrive%\adwcleaner\quarantine\exuieaoeii\engine
%sysdrive%\adwcleaner\quarantine\idcdjoyapn\engine
%sysdrive%\windows.old\users\default\appdata\local\pokki\engine

ThreatInfo has observed Launcher (1).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.

Launcher.dll
___ocnsis.dll
Launcher.dll.vir
Launcher.dll.pcpquar
Launcher (1).dll

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

16.8%
9.4%
7.7%
6.9%
5.6%
5.4%
4.0%
3.5%
3.2%
3.2%
3.2%
2.5%
2.3%
1.9%
1.7%
1.4%
1.4%
1.4%
1.2%
1.1%
1.1%
1.0%
1.0%
1.0%
0.9%
0.9%
0.9%
0.7%
0.7%
0.6%
0.6%
0.5%
0.5%
0.5%
0.5%
0.5%
0.4%
0.4%
0.4%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%

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

Windows 10 51.9%
Windows 8.1 47.2%
Windows 8 0.9%

The most common operating system signal for Launcher (1).dll is Windows 10 with 51.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.

Launcher (1).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: 0x10000000
Entry Address: 0x000e58df

PE Sections:

Name Size of data MD5
.text 1190912 4d0d63a3654bf81d45e7d27d8378d77a
.rdata 186880 5ca6b125118c7ecb085776f19e3993ed
.data 25600 f50cb49431ee1d54352e395b24932844
.tls 512 bf619eac0cdf3f68d496ea9344137e8b
.shared 512 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 399360 fd1570ed72ca6f8b1dca6996ce9aa932
.reloc 81920 13f738bda22455196e4b0f3007d25920

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: