GridinSoft Threat Intelligence

jcPKCS11-2.dll file report

Under review File reputation report
MD5 8529567ceb4921810c149e45c1de7721
Latest seen 2025-11-10 23:01:45 (6 months ago)
First seen 2025-10-05 23:00:56 (7 months ago)
Size 5 MB
Publisher Aladdin R.D.
Signed by ALADDIN R.D. AO

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-10-05 23:00:56 (7 months ago); latest analysis 2025-11-10 23:01:45 (6 months ago).

Publisher context

Company metadata: Aladdin R.D..

Digital signature

Signed by ALADDIN R.D. AO. 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.

jcPKCS11-2.dll is a Windows file recorded in the ThreatInfo database. The reported company name is Aladdin R.D.. The current detection status is Undefined, based on the latest analysis from 2025-11-10 23:01:45 (6 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.

Company Name: Aladdin R.D.
MD5: 8529567ceb4921810c149e45c1de7721
Size: 5 MB
First Published: 2025-10-05 23:00:56 (7 months ago)
Latest Published: 2025-11-10 23:01:45 (6 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-11-10 23:01:45 (6 months ago)
Signed By: ALADDIN R.D. AO
Status: Valid

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

%programfiles%\tensor\saby\25.4139.15\service\modules\clientcryptography
%programfiles%\tensor\saby\25.4139.17\service\modules\clientcryptography
%programfiles%\tensor\saby\25.5218.38\service\modules\clientcryptography
%programfiles%\tensor\saby\25.5218.32\service\modules\clientcryptography

ThreatInfo has observed jcPKCS11-2.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 100.0%

The most common operating system signal for jcPKCS11-2.dll 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.

jcPKCS11-2.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 0x00319889
Image base 0x10000000

PE Sections:

Sections 5
Raw data 5352448

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

.text 3658752 bytes · 68.4% of section data
MD5 b7f3e96218c05e3ea50db6a707634d58
.rdata 1390592 bytes · 26.0% of section data
MD5 fea647d5eba565ce3a85bd330d6400d2
.data 98304 bytes · 1.8% of section data
MD5 8fbb504e86e33b2b0583fd598f2cde86
.rsrc 1536 bytes · 0.0% of section data
MD5 c1d729c121eea31248858148b5d3a1ac
.reloc 203264 bytes · 3.8% of section data
MD5 76baebe9a824d267624030551eab5125

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 8529567ceb4921810c149e45c1de7721.
  • 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.