GridinSoft Threat Intelligence

TPFCustom.dll file report

Under review File reputation report
MD5 6aabae224ccd52123ddd5eb7d9cd1acc
Latest seen 2026-03-30 23:00:39 (2 months ago)
First seen 2026-03-30 23:00:39 (2 months ago)
Size 3 MB
Product Tenio

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-03-30 23:00:39 (2 months ago); latest analysis 2026-03-30 23:00:39 (2 months ago).

Publisher context

Product metadata: Tenio.

Digital signature

Signed by Tencent Technology (Shenzhen) Company Limited. 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.

TPFCustom.dll is a Windows file recorded in the ThreatInfo database. It is associated with Tenio. The current detection status is Undefined, based on the latest analysis from 2026-03-30 23:00:39 (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: Tenio
MD5: 6aabae224ccd52123ddd5eb7d9cd1acc
Size: 3 MB
First Published: 2026-03-30 23:00:39 (2 months ago)
Latest Published: 2026-03-30 23:00:39 (2 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-03-30 23:00:39 (2 months ago)

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

%sysdrive%\delta force\launcher

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

TPFCustom.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. 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 GUI
Entry point 0x00195c8d
Image base 0x10000000

PE Sections:

Sections 5
Raw data 3374592

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

.text 2541056 bytes · 75.3% of section data
MD5 d624caa222a12f22a837e5653885a701
.rdata 692736 bytes · 20.5% of section data
MD5 8d5623b587c2348a51191558d68dd8eb
.data 26624 bytes · 0.8% of section data
MD5 747181b3b0c01e0a9df4bac9ddf9e49d
.rsrc 1024 bytes · 0.0% of section data
MD5 6fc777439f57471db68e52e6e02b4f27
.reloc 113152 bytes · 3.4% of section data
MD5 dc5fa89bba7d3f5fc09abd467068cf45

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 6aabae224ccd52123ddd5eb7d9cd1acc.
  • 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.