GridinSoft Threat Intelligence

urlproc.dll file report

Under review File reputation report
MD5 75db43606be4fe1a65eb81f68735c1c5
Latest seen 2026-01-11 23:00:27 (4 months ago)
First seen 2018-02-17 17:05:05 (8 years ago)
Size 709 KB
Publisher 360.cn
Product 360安全卫士
Signed by Qihoo 360 Software (Beijing) Company Limited

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-02-17 17:05:05 (8 years ago); latest analysis 2026-01-11 23:00:27 (4 months ago).

Publisher context

Company metadata: 360.cn. Product metadata: 360安全卫士.

Digital signature

Signed by Qihoo 360 Software (Beijing) Company Limited. 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

urlproc.dll is a Windows file recorded in the ThreatInfo database. It is associated with 360安全卫士. The reported company name is 360.cn. The current detection status is Undefined, based on the latest analysis from 2026-01-11 23:00:27 (4 months 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: 360安全卫士
Company Name: 360.cn
MD5: 75db43606be4fe1a65eb81f68735c1c5
Size: 709 KB
First Published: 2018-02-17 17:05:05 (8 years ago)
Latest Published: 2026-01-11 23:00:27 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-11 23:00:27 (4 months ago)

Overview

Signed By: Qihoo 360 Software (Beijing) Company Limited
Status: Valid

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

%appdata%\360se6\application
%localappdata%\360chrome\chrome\application
%profile%\dmin\local settings\application data\360chrome\chrome\application
%profile%\дминистратор.microsof-7c709f\local settings\application data\360chrome\chrome\application

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

Top country China
Share 45.2%
Low High activity

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

OS Version:

Windows 10 53.8%
Windows 7 24.7%
Windows Server 2012 R2 12.9%
Windows Server 2008 R2 3.2%
Windows XP 3.2%
Windows 8.1 2.2%

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

urlproc.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 0x00068b78
Image base 0x10000000

PE Sections:

Sections 7
Raw data 710656

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

.text 563712 bytes · 79.3% of section data
MD5 e635663d7b987c84baf517aacccd08cb
.rdata 93696 bytes · 13.2% of section data
MD5 0e3bd4daf14611058e54ec95252fb832
.data 16896 bytes · 2.4% of section data
MD5 32d3cb503b0fbb92f7f2eeaef4b65894
.MAGIC 512 bytes · 0.1% of section data
Uncommon name
MD5 fbbf7b606066366cf16f2769f2148a66
.SHARE 512 bytes · 0.1% of section data
Uncommon name
MD5 43b5d570c25a9312850173830aec4c9f
.rsrc 2048 bytes · 0.3% of section data
MD5 d1e8f5c802ef0692ad9be69c249329b4
.reloc 33280 bytes · 4.7% of section data
MD5 76c90bde79690a9521fb8840340d4bb4

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 75db43606be4fe1a65eb81f68735c1c5.
  • 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.