GridinSoft Threat Intelligence

BouncyCastle.Crypto.dll file report

Under review File reputation report
MD5 cc986fa07d3a886e7f5343e6a4da90fa
Latest seen 2024-01-02 23:34:53 (2 years ago)
First seen 2017-05-21 04:03:33 (9 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 04:03:33 (9 years ago); latest analysis 2024-01-02 23:34:53 (2 years ago).

Publisher context

Company metadata: The Legion of the Bouncy Castle. Product metadata: Bouncy Castle for .NET.

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.

BouncyCastle.Crypto.dll is a Windows file recorded in the ThreatInfo database. It is associated with Bouncy Castle for .NET. The reported company name is The Legion of the Bouncy Castle. The current detection status is Undefined, based on the latest analysis from 2024-01-02 23:34:53 (2 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: Bouncy Castle for .NET
Company Name: The Legion of the Bouncy Castle
MD5: cc986fa07d3a886e7f5343e6a4da90fa
Size: 1 MB
First Published: 2017-05-21 04:03:33 (9 years ago)
Latest Published: 2024-01-02 23:34:53 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-02 23:34:53 (2 years ago)
%programfiles%\free youtube downloader
%programfiles%\livesurf client
%localappdata%\autodengi app
%programfiles%
%localappdata%

ThreatInfo has observed BouncyCastle.Crypto.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 7 50.6%
Windows 10 40.9%
Windows 8.1 6.7%
Windows 8 0.8%
Windows Vista 0.4%
Windows XP 0.4%
Windows Server 2008 R2 0.1%

The most common operating system signal for BouncyCastle.Crypto.dll is Windows 7 with 50.6% 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.

BouncyCastle.Crypto.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 0x0016dfbe
Image base 0x00400000

.NET Info:

MVID: 290396c3-369c-4d82-bd89-e4573780d525

PE Sections:

Sections 3
Raw data 1499136

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

.text 1490944 bytes · 99.5% of section data
MD5 13d9c073e74e41c0c08e4e521d886f6e
.rsrc 4096 bytes · 0.3% of section data
MD5 bf79863098867e1e4e93038f80321709
.reloc 4096 bytes · 0.3% of section data
MD5 b6a16367afaa4a718cb9d353b814e156

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 cc986fa07d3a886e7f5343e6a4da90fa.
  • 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.