Threat LensFile scan report

Is pcre2-16.dll safe?

Verdict
Safe

No antivirus engine detected this established, verified CD PROJEKT DLL, while five signer-matched files received consistent benign assessments despite isolated behavioral mappings.

The DLL drew no detections from 74 antivirus engines, including 17 reporting tier-1 engines, and carries a verified CD PROJEKT S.A. signature. Its broad prevalence and five benign signer-matched precedents outweigh the isolated T1055 and T1562.001 behavioral mappings, which were not accompanied by a malicious sandbox conclusion.

Use with normal care

Use the DLL only as part of its original, officially obtained CD PROJEKT installation. Keep endpoint protection enabled and replace the file through the product's verification or repair feature if its origin is uncertain.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 74 flagged
Flagged 0No detection 74
Digital specimenpcre2-16.dll143de9f4229cc5fac9…c5fcb4f5ea7808
Size414.6 KB
Code signingCD PROJEKT S.A.
SandboxRuntime complete
First seen1y ago
Evidence3 priority signals
0 of 74 antivirus engines flagged the file.

Recommended next actions

01

Before using

Use it only as part of software obtained from the developer's official site or another source you independently trust.

02

If you already used it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

94%Confidence
Very high
Analyst conclusion

The DLL drew no detections from 74 antivirus engines, including 17 reporting tier-1 engines, and carries a verified CD PROJEKT S.A. signature. Its broad prevalence and five benign signer-matched precedents outweigh the isolated T1055 and T1562.001 behavioral mappings, which were not accompanied by a malicious sandbox conclusion.

Where this verdict could be wrong3 caveats
  • behaviour.offensiveTechniques includes T1055 and T1562.001, and MalwareTips.Synth.ProcessInjection fired; however, the saved mapping does not establish the exact method or intent.
  • signing.signerStats.totalSamples=1 provides limited standalone publisher-history depth, though five signer-matched prior verdicts independently support the signature.
  • contactedHosts is null, so no complete host-reputation cross-check is available; the sandbox recorded no contacted domains, IPs, or URLs.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Use the DLL only as part of its original, officially obtained CD PROJEKT installation. Keep endpoint protection enabled and replace the file through the product's verification or repair feature if its origin is uncertain.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    0 of 74 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded
  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 14MITRE ATT&CK techniques
  • 15spawned processes
  • 0network contacts
  • 40filesystem & mutex artifacts
Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & FAQ

Complete recovery guidance and answers for the next decision.

What to do now

This file appears low risk based on the evidence available now.

  1. Recovery step 01

    Use it only as part of software obtained from the developer's official site or another source you independently trust.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

  3. Recovery step 03

    Keep your antivirus and Windows updates switched on so you stay protected.

Safety FAQ

Direct answers grounded in the saved verdict and evidence in this report.

7 evidence-based answers
Is pcre2-16.dll safe?
Evidence-based answer
pcre2-16.dll appears safe. 0 of 74 antivirus engines flagged it. It carries a verified digital signature from CD PROJEKT S.A.. Use it only as part of software obtained from the developer's official site or another source you independently trust.
What is pcre2-16.dll?
Evidence-based answer
pcre2-16.dll is a Windows library or loadable module, about 415 KB. Our analysis did not identify a verdict-driving threat signal. It carries a verified digital signature from CD PROJEKT S.A.. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected pcre2-16.dll?
Evidence-based answer
None — 0 of 74 antivirus engines flagged pcre2-16.dll. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
Is pcre2-16.dll digitally signed?
Evidence-based answer
Yes — pcre2-16.dll carries a valid digital signature from CD PROJEKT S.A., which confirms the file hasn't been tampered with since that publisher signed it. A valid signature is a positive signal, but note that malware is occasionally signed with stolen or abused certificates, so it isn't proof of safety on its own.
What is the SHA-256 hash of pcre2-16.dll?
Evidence-based answer
The SHA-256 hash of pcre2-16.dll is 143de9f4229cc5fac90b323ef9a655c0fdc819be7a47b63d08c5fcb4f5ea7808, and its MD5 is c8fd67da418cbbf2891912d29298af01. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
Is it safe to use pcre2-16.dll?
Evidence-based answer
Based on the recorded evidence, pcre2-16.dll has a low observed risk and is properly signed. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
How up to date is this analysis of pcre2-16.dll?
Evidence-based answer
This report reflects the scan run on September 23, 2026. Because a file's hash never changes, the identity of pcre2-16.dll is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.