GridinSoft Threat Intelligence

obkconp.dll file report

Clean record File reputation report
MD5 2a598a971c58525121a8408e04ada674
Latest seen 2024-11-23 23:01:34 (a year ago)
First seen 2024-11-23 23:01:34 (a year ago)
Size 452 KB
Publisher Orange
Signed by Bitdefender SRL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-11-23 23:01:34 (a year ago); latest analysis 2024-11-23 23:01:34 (a year ago).

Publisher context

Company metadata: Orange. Product metadata: Suite de Sécurité Orange.

Digital signature

Signed by Bitdefender SRL. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

obkconp.dll is a Windows file recorded in the ThreatInfo database. It is associated with Suite de Sécurité Orange. The reported company name is Orange. The current detection status is Clean, based on the latest analysis from 2024-11-23 23:01:34 (a year ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Suite de Sécurité Orange
Company Name: Orange
MD5: 2a598a971c58525121a8408e04ada674
Size: 452 KB
First Published: 2024-11-23 23:01:34 (a year ago)
Latest Published: 2024-11-23 23:01:34 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2024-11-23 23:01:34 (a year ago)
Signed By: Bitdefender SRL
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%programfiles%\orange

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

Windows 10 100.0%

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

obkconp.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00047cb0
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 450048

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

.text 310272 bytes · 68.9% of section data
MD5 9da22bac277bb713b012d359f65ce83e
.rdata 93696 bytes · 20.8% of section data
MD5 dd90cc155a28e043acf5572aa120f791
.data 7680 bytes · 1.7% of section data
MD5 4ccfa50557a30789ce42315577cd8474
.pdata 15872 bytes · 3.5% of section data
MD5 ef5719d5224865098d18d7a18592420c
.rsrc 19456 bytes · 4.3% of section data
MD5 6c039217770e7e5d5aa3bc36330e0914
.reloc 3072 bytes · 0.7% of section data
MD5 91be5a32fad6752595ae5f008e8f6a5e

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 2a598a971c58525121a8408e04ada674.
  • 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.