Why it matters
Evidence available for this file
No final classification is available yet.
Programs that inject advertising, change browser behavior, or monetize traffic through bundled components. Related Adware reports help compare this file with nearby detections, publishers, and hashes.
First seen 2020-12-11 11:42:00 (5 years ago); latest analysis 2021-03-07 04:25:57 (5 years ago).
Signed by Beijing Qihu Technology Co., Ltd.. The signature is reported as valid, but signed files can still be bundled or abused.
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
lMkKlPiJqSsKvYcU.tmp 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 2021-03-07 04:25:57 (5 years ago). ThreatInfo groups this verdict with Adware 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: | 360安全浏览器 |
| Company Name: | 360.cn |
| MD5: | 5a7788acf8af61eb7b8c38b44f7b6fa5 |
| Size: | 2 MB |
| First Published: | 2020-12-11 11:42:00 (5 years ago) |
| Latest Published: | 2021-03-07 04:25:57 (5 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2021-03-07 04:25:57 (5 years ago) |
Overview
| Signed By: | Beijing Qihu Technology Co., Ltd. |
| Status: | Valid |
The signature on lMkKlPiJqSsKvYcU.tmp 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% |
ThreatInfo has observed lMkKlPiJqSsKvYcU.tmp 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 lMkKlPiJqSsKvYcU.tmp across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Taiwan with 75.0% 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 lMkKlPiJqSsKvYcU.tmp is Windows 10 with 50.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.
Analysis
lMkKlPiJqSsKvYcU.tmp 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.
c2e2e6dea25da4350a0d499e86503117
d381204abca124cd04e88b51f1b12bc9
410b9c896741a8a92a7bce2deb0941bf
7f7d130ef75f864596b0c5a66504aab9
bf619eac0cdf3f68d496ea9344137e8b
14a489d049f4eebe2d3cb422ae5d1248
842689af09e7bf563672a4b43f1a2286
bf619eac0cdf3f68d496ea9344137e8b
d2da681910ac7857d3574f9996e121ce
40a6e4a95ddeefed65c765f968315f81
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.