GridinSoft Threat Intelligence

git2.dll file report

Under review File reputation report
MD5 8b831946731da671f51cfcd768a8ac6b
Latest seen 2023-12-31 23:34:12 (2 years ago)
First seen 2023-12-31 23:34:12 (2 years ago)
Size 1 MB
Product libgit2
Signed by Adobe Inc.

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2023-12-31 23:34:12 (2 years ago); latest analysis 2023-12-31 23:34:12 (2 years ago).

Publisher context

Product metadata: libgit2.

Digital signature

Signed by Adobe Inc.. 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.

git2.dll is a Windows file recorded in the ThreatInfo database. It is associated with libgit2. The current detection status is Undefined, based on the latest analysis from 2023-12-31 23:34:12 (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: libgit2
MD5: 8b831946731da671f51cfcd768a8ac6b
Size: 1 MB
First Published: 2023-12-31 23:34:12 (2 years ago)
Latest Published: 2023-12-31 23:34:12 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-31 23:34:12 (2 years ago)
Signed By: Adobe Inc.
Status: Valid

The signature on git2.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%\adobe1\adobe after effects 2022

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

git2.dll is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x000d7100
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 1263616

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

.text 978432 bytes · 77.4% of section data
MD5 be3fd8ee3d6af57c87c5ba80453f0d62
.rdata 212480 bytes · 16.8% of section data
MD5 400c2dde9b7dc8a145ec2972583cc36f
.data 17920 bytes · 1.4% of section data
MD5 94c5234def876dcf7431d1f95e90e1e4
.pdata 50176 bytes · 4.0% of section data
MD5 7eedb7effaf9cdbe57166d6a4bc0659a
.rsrc 1536 bytes · 0.1% of section data
MD5 bb13a45609c6a6d2b5b5aee03f9e5335
.reloc 3072 bytes · 0.2% of section data
MD5 cc4cdd7d8e534a413d5d11e3f1b54e28

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 8b831946731da671f51cfcd768a8ac6b.
  • 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.