GridinSoft Threat Intelligence

chrome.dll file report

Under review File reputation report
MD5 3a90506a748f99deb7f9550682f225d6
Latest seen 2025-12-14 23:00:43 (5 months ago)
First seen 2025-12-14 23:00:43 (5 months ago)
Size 238 MB
Publisher The Ninja Browser Authors
Product Ninja Browser
Signed by OOO MAKTE

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-12-14 23:00:43 (5 months ago); latest analysis 2025-12-14 23:00:43 (5 months ago).

Publisher context

Company metadata: The Ninja Browser Authors. Product metadata: Ninja Browser.

Digital signature

Signed by OOO MAKTE. 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

chrome.dll is a Windows file recorded in the ThreatInfo database. It is associated with Ninja Browser. The reported company name is The Ninja Browser Authors. The current detection status is Undefined, based on the latest analysis from 2025-12-14 23:00:43 (5 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: Ninja Browser
Company Name: The Ninja Browser Authors
MD5: 3a90506a748f99deb7f9550682f225d6
Size: 238 MB
First Published: 2025-12-14 23:00:43 (5 months ago)
Latest Published: 2025-12-14 23:00:43 (5 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-12-14 23:00:43 (5 months ago)

Overview

Signed By: OOO MAKTE
Status: Valid

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

%programfiles%\ninjabrowser\ninjabrowser\application

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

Top country Israel
Share 100.0%
Low High activity

The strongest geographic signal for this file is Israel with 100.0% 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 100.0%

The most common operating system signal for chrome.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.

Analysis

chrome.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. 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 CUI
Entry point 0x0ceb3050
Image base 0x10000000

PE Sections:

Sections 11
Raw data 250379264

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

.text 217157632 bytes · 86.7% of section data
Large raw data
MD5 f108efa0bac5bead32aba2ea6098ff19
.rdata 23053824 bytes · 9.2% of section data
Large raw data
MD5 02aed971ed0aa112ba1aaa9862565105
.data 1047552 bytes · 0.4% of section data
MD5 a56d0099be4da09c54c5c691d3356534
.fptable 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rodata 2560 bytes · 0.0% of section data
MD5 4242fe36f600876ab6f794593d66ac10
.tls 1024 bytes · 0.0% of section data
MD5 9c85d25f1d319203bc3a2b6d48c63ab3
CPADinfo 512 bytes · 0.0% of section data
Uncommon name
MD5 842689af09e7bf563672a4b43f1a2286
malloc_h 1536 bytes · 0.0% of section data
Uncommon name
MD5 426f87a6f5ac42dd0c1912504e9caace
prot 512 bytes · 0.0% of section data
Uncommon name
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 102400 bytes · 0.0% of section data
MD5 0ac40d4e5c97a0a5ddaafe122ba1cca3
.reloc 9011200 bytes · 3.6% of section data
Large raw data
MD5 a0dfb21a57120ab067cdc5d7ae7dcc0b

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 3a90506a748f99deb7f9550682f225d6.
  • 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.