GridinSoft Threat Intelligence

CoreRS.dll file report

Under review File reputation report
MD5 2bd27ebc3a0b5e2a230b204d5c96dbcb
Latest seen 2021-01-11 12:16:47 (5 years ago)
First seen 2020-01-04 19:36:28 (6 years ago)
Size 378 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-04 19:36:28 (6 years ago); latest analysis 2021-01-11 12:16:47 (5 years ago).

Publisher context

Product metadata: CoreRS.dll Module.

Digital signature

Signed by Sorentio Systems Ltd. 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.

CoreRS.dll is a Windows file recorded in the ThreatInfo database. It is associated with CoreRS.dll Module. The current detection status is Undefined, based on the latest analysis from 2021-01-11 12:16:47 (5 years 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.

Product Name: CoreRS.dll Module
MD5: 2bd27ebc3a0b5e2a230b204d5c96dbcb
Size: 378 KB
First Published: 2020-01-04 19:36:28 (6 years ago)
Latest Published: 2021-01-11 12:16:47 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 12:16:47 (5 years ago)
Signed By: Sorentio Systems Ltd
Status: Valid

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

%commondir%

ThreatInfo has observed CoreRS.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 XP 52.9%
Windows 10 29.4%
Windows 7 17.6%

The most common operating system signal for CoreRS.dll is Windows XP with 52.9% 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.

CoreRS.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 0x000339d6
Image base 0x10000000

PE Sections:

Sections 5
Raw data 360960

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

.text 257536 bytes · 71.3% of section data
MD5 464d055297fa9ba5383400dc619e9917
.rdata 61440 bytes · 17.0% of section data
MD5 0793f9329f4d1b346e0d146792c52b62
.data 9728 bytes · 2.7% of section data
MD5 ec51651c1298c0d9bff48269245b271f
.rsrc 8704 bytes · 2.4% of section data
MD5 f57eb2ab585d42e63336ba9c28f545e2
.reloc 23552 bytes · 6.5% of section data
MD5 aa8e74fd299ebdc4c1c56e457531eb1c

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