GridinSoft Threat Intelligence

Cudo Miner Core.exe file report

Under review File reputation report
MD5 1a0248162c2ba58259998a3f8fa3cc37
Latest seen 2021-11-26 21:04:17 (4 years ago)
First seen 2021-11-26 21:04:17 (4 years ago)
Size 54 MB
Publisher Cudo Miner
Product Cudo Miner

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-11-26 21:04:17 (4 years ago); latest analysis 2021-11-26 21:04:17 (4 years ago).

Publisher context

Company metadata: Cudo Miner. Product metadata: Cudo Miner.

Digital signature

Signed by Cudo Ventures, Ltd.. The signature is reported as valid, but signed files can still be bundled or abused.

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.

Cudo Miner Core.exe is a Windows file recorded in the ThreatInfo database. It is associated with Cudo Miner. The reported company name is Cudo Miner. The current detection status is Undefined, based on the latest analysis from 2021-11-26 21:04:17 (4 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: Cudo Miner
Company Name: Cudo Miner
MD5: 1a0248162c2ba58259998a3f8fa3cc37
Size: 54 MB
First Published: 2021-11-26 21:04:17 (4 years ago)
Latest Published: 2021-11-26 21:04:17 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-11-26 21:04:17 (4 years ago)
Signed By: Cudo Ventures, Ltd.
Status: Valid

The signature on Cudo Miner Core.exe 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.

Windows 10 100.0%

The most common operating system signal for Cudo Miner Core.exe 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.

Cudo Miner Core.exe is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x0004eaee
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 40641536

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

.text 23494656 bytes · 57.8% of section data
Large raw data
MD5 eecb3eef0bde1c4b3a05b286dde6cb27
.rdata 15457280 bytes · 38.0% of section data
Large raw data
MD5 4997ece446d513e9e9e6c02a96c5a53d
.data 193536 bytes · 0.5% of section data
MD5 14a47e9fc824def0078e2a428efa355d
.pdata 1069056 bytes · 2.6% of section data
MD5 f373465c543409408f6dd07343f160ec
.idata 17920 bytes · 0.0% of section data
MD5 2399356a74cf7236792f4822ee5d1431
.tls 1024 bytes · 0.0% of section data
MD5 da05337af5f9a7a34acc4f4783eaea42
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 25b3d89298438c873643dd7834a4cccf
.rsrc 158208 bytes · 0.4% of section data
MD5 57929424b0beb4ce0aae41fcf5e60b81
.reloc 249344 bytes · 0.6% of section data
MD5 5625b97ca48c4ae20fe84bbbe5f07445

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 1a0248162c2ba58259998a3f8fa3cc37.
  • 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.