GridinSoft Threat Intelligence

Launcher.dll#FBDD8650E09C59D7 file report

Under review File reputation report
MD5 300f04d5075d5dab19fd197eb01f7a80
Latest seen 2024-08-15 23:01:30 (2 years ago)
First seen 2017-05-24 12:03:09 (8 years ago)
Size 523 KB
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-24 12:03:09 (8 years ago); latest analysis 2024-08-15 23:01:30 (2 years 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.dll#FBDD8650E09C59D7 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 2024-08-15 23:01:30 (2 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.

Product Name: Pokki
Company Name: SweetLabs, Inc.
MD5: 300f04d5075d5dab19fd197eb01f7a80
Size: 523 KB
First Published: 2017-05-24 12:03:09 (8 years ago)
Latest Published: 2024-08-15 23:01:30 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-15 23:01:30 (2 years ago)
Signed By: Pokki
Status: Valid

The signature on Launcher.dll#FBDD8650E09C59D7 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
%localappdata%\pokki
%temp%
%sysdrive%\adwcleaner\quarantine\idcdjoyapn
%windir%\serviceprofiles\localservice\appdata\local\pokki
%windir%\serviceprofiles\networkservice\appdata\local\pokki
%sysdrive%\adwcleaner\quarantine\v1\20180913.124013\8\pokki
%sysdrive%\windows.old\users\default\appdata\local\pokki
%sysdrive%\windows.old\users\yousufislam\appdata\local\pokki

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

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.

Windows 10 69.9%
Windows 8.1 30.1%

The most common operating system signal for Launcher.dll#FBDD8650E09C59D7 is Windows 10 with 69.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.dll#FBDD8650E09C59D7 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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x000343c8
Image base 0x10000000

PE Sections:

Sections 6
Raw data 528384

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 384000 bytes · 72.7% of section data
MD5 342d8ca8cff4a8ce54888e24e3738100
.rdata 82944 bytes · 15.7% of section data
MD5 74440a9e3e18feb207f24134ea0582e3
.data 13312 bytes · 2.5% of section data
MD5 d4d3ae8104c85482b2440ce0c1dbbe04
.shared 512 bytes · 0.1% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 21504 bytes · 4.1% of section data
MD5 dfbb2b81cc7d6a80f04de2b204523c58
.reloc 26112 bytes · 4.9% of section data
MD5 dbd7039bf8c2b56768f64642ea2e3ebe

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.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 300f04d5075d5dab19fd197eb01f7a80.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.