GridinSoft Threat Intelligence

___ocnsis.dll file report

Under review File reputation report
MD5 518eeab387d03175ac167d0006591fc2
Latest seen 2022-01-25 21:44:43 (4 years ago)
First seen 2017-06-24 13:02:28 (8 years ago)
Size 3 MB
Publisher SweetLabs, Inc.
Product Pokki
Signed by Pokki

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2017-06-24 13:02:28 (8 years ago); latest analysis 2022-01-25 21:44:43 (4 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.

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.

File context

___ocnsis.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 2022-01-25 21:44:43 (4 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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: 518eeab387d03175ac167d0006591fc2
Size: 3 MB
First Published: 2017-06-24 13:02:28 (8 years ago)
Latest Published: 2022-01-25 21:44:43 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-01-25 21:44:43 (4 years ago)

Overview

Signed By: Pokki
Status: Valid

The signature on ___ocnsis.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:

%temp%\nsmcf13.tmp
%temp%\nsx218c.tmp
%temp%
%mydoc%\usb\luis\appdata\local\temp
%desktop%\enzo\appdata\local\temp
%desktop%\carlos\carlos\appdata\local\temp

ThreatInfo has observed ___ocnsis.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 ___ocnsis.dll across 7 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Spain
Share 29.4%
Low High activity

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

OS Version:

Windows 8.1 82.4%
Windows 10 17.6%

The most common operating system signal for ___ocnsis.dll is Windows 8.1 with 82.4% 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

___ocnsis.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.

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

PE Sections:

Sections 7
Raw data 3249152

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

.text 2348544 bytes · 72.3% of section data
MD5 bc5a1f615a96700c995c2207400ceba3
.rdata 516608 bytes · 15.9% of section data
MD5 f61e937ecbc0d7969bae2bbde8054d84
.data 62464 bytes · 1.9% of section data
MD5 663bba990b9683ac1294c10fd2d519c1
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.shared 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 169984 bytes · 5.2% of section data
MD5 f2f0bc8a11a5e9d29c2422c498b78a4c
.reloc 150528 bytes · 4.6% of section data
MD5 e698702e0f117eaa15e8594f7a62d126

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 518eeab387d03175ac167d0006591fc2.
  • 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. Use the PUP category to compare similar reports.