GridinSoft Threat Intelligence

_poly1305.pyd file report

Under review File reputation report
MD5 01112c14e67938e8c06c14beea5d889b
Latest seen 2022-02-26 23:19:00 (4 years ago)
First seen 2022-02-26 23:19:00 (4 years ago)
Size 25 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-02-26 23:19:00 (4 years ago); latest analysis 2022-02-26 23:19:00 (4 years ago).

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.

_poly1305.pyd is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-02-26 23:19:00 (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.

MD5: 01112c14e67938e8c06c14beea5d889b
Size: 25 KB
First Published: 2022-02-26 23:19:00 (4 years ago)
Latest Published: 2022-02-26 23:19:00 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-02-26 23:19:00 (4 years ago)
%commonappdata%\majaovca\chia-blockchain\app-1.2.9\resources\app.asar.unpacked\daemon\crypto

ThreatInfo has observed _poly1305.pyd 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.

100.0%

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

Windows 10 100.0%

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

_poly1305.pyd is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00001360
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 24576

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

.text 12800 bytes · 52.1% of section data
MD5 20c8fb3cd5efaa2f3039dcab5011b022
.rdata 8192 bytes · 33.3% of section data
MD5 19b6ba692df534e29cc0625242b6d0fe
.data 512 bytes · 2.1% of section data
MD5 2ec7d10743fa5c6683249956503708c4
.pdata 1536 bytes · 6.3% of section data
MD5 523241666a65e036e0340e3f690620d1
_RDATA 512 bytes · 2.1% of section data
Uncommon name
MD5 851c48583b25e36e9e4e0aec8e7277a6
.rsrc 512 bytes · 2.1% of section data
MD5 7f77341ca10dad16840e75bf70bc8baf
.reloc 512 bytes · 2.1% of section data
MD5 4cb11f1e0c66c678b1b6b3d7873f4f66

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 01112c14e67938e8c06c14beea5d889b.
  • 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.