GridinSoft Threat Intelligence

BouncyCastle.Crypto.dll file report

Under review File reputation report
MD5 3cf6bf0e0a27f3665edd6362d137e4cc
Latest seen 2026-03-02 23:00:53 (2 months ago)
First seen 2018-07-23 15:13:23 (7 years ago)
Size 2 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2018-07-23 15:13:23 (7 years ago); latest analysis 2026-03-02 23:00:53 (2 months ago).

Publisher context

Company metadata: The Legion of the Bouncy Castle Inc.. 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 Inc.. The current detection status is Undefined, based on the latest analysis from 2026-03-02 23:00:53 (2 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.

Product Name: Bouncy Castle for .NET
Company Name: The Legion of the Bouncy Castle Inc.
MD5: 3cf6bf0e0a27f3665edd6362d137e4cc
Size: 2 MB
First Published: 2018-07-23 15:13:23 (7 years ago)
Latest Published: 2026-03-02 23:00:53 (2 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-03-02 23:00:53 (2 months ago)
%appdata%\sphere\modulecache\bouncycastle.crypto
%programfiles%
%commonappdata%
%localappdata%
%appdata%\temp\misa.sme2019\winroot\misa jsc\misa sme.net 2019
%appdata%\temp\sme2020\winroot\misa jsc\misa sme.net 2020
%appdata%\temp\misa.sme2019\winroot\misa jsc\misa sme.net 2020

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 10 67.1%
Windows 7 25.9%
Windows 8.1 5.4%
Windows 8 0.9%
Windows Vista 0.5%
Windows Server 2016 0.2%

The most common operating system signal for BouncyCastle.Crypto.dll is Windows 10 with 67.1% 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 0x0022033e
Image base 0x00400000

.NET Info:

MVID: 2c1e8153-b25b-4cde-9676-eedaf8a00392

PE Sections:

Sections 3
Raw data 2232320

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

.text 2224128 bytes · 99.6% of section data
MD5 aa5fc62398a9a4c658a0f1dd49d1ef33
.rsrc 4096 bytes · 0.2% of section data
MD5 dcbb46779fd225afc2307ff3931b2857
.reloc 4096 bytes · 0.2% of section data
MD5 140141d31cb7bdce1b2de4ff3250cc67

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