GridinSoft Threat Intelligence
Launcher (1).dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2017-06-06 15:09:54 (8 years ago); latest analysis 2025-01-09 23:00:50 (a year ago).
Company metadata: SweetLabs, Inc.. Product metadata: Pokki.
Signed by Pokki. The signature is reported as valid, but signed files can still be bundled or abused.
This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.
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
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-01-09 23:00:50 (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: | Pokki |
| Company Name: | SweetLabs, Inc. |
| MD5: | 9d7b1c0785c4b081d07e7330a7da9518 |
| Size: | 1 MB |
| First Published: | 2017-06-06 15:09:54 (8 years ago) |
| Latest Published: | 2025-01-09 23:00:50 (a year ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2025-01-09 23:00:50 (a year ago) |
Overview
| 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.
Common Places:
| %localappdata%\pokki\engine |
| %sysdrive%\adwcleaner\quarantine\files\ibwfzvegtyjocfyzdqaurxlewpwmcqpx\engine |
| %sysdrive%\adwcleaner\quarantine\files\cvdzzvesszzfgrwfigxefhgnaeeejbmt\engine |
| %sysdrive%\adwcleaner\quarantine\files\msmnmrhjuwlbrpvukasrqbrojecosqho\engine |
| %sysdrive%\adwcleaner\quarantine\files\hdmngrfcbwrwynlmsnxvlapnyjedtpar\engine |
| %temp%\nsba6a8.tmp |
| %temp%\nsg3fff.tmp |
| %sysdrive%\$recycle.bin\s-1-5-21-2966412212-3357225099-3928630548-1001\$rqs4krx.tmp |
| %sysdrive%\windows.old\users\kirill\appdata\local\temp\nsndd38.tmp |
| %sysdrive%\adwcleaner\quarantine\files\fucxcyiljimkvzhihizqpynhuvdfralk\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.
File Names:
3 observed namesThis 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.
Geographic signal
Observed country distribution
ThreatInfo has seen Launcher (1).dll across 36 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 14.2% 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 Launcher (1).dll is Windows 10 with 55.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
Launcher (1).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.
f49053d8c5b4786b97f96b826bc321da
9fcae849aa1bdef68c3e9f132a091041
e0c5419c04f08688b00f17106206485e
bf619eac0cdf3f68d496ea9344137e8b
bf619eac0cdf3f68d496ea9344137e8b
646d0d245185b8da893a212a0c07165f
5477e1adfb8cf99bc7b2745e3d380fc6
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.