GridinSoft Threat Intelligence

TBNHlpr_x64_exe file report

Under review File reputation report
MD5 97215c5841e988a436773e321515fa69
Latest seen 2025-02-07 23:01:33 (a year ago)
First seen 2017-05-21 07:08:26 (8 years ago)
Size 189 KB
Publisher APN
Signed by APN LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-21 07:08:26 (8 years ago); latest analysis 2025-02-07 23:01:33 (a year ago).

Publisher context

Company metadata: APN. Product metadata: APN Toolbar Notifier Helper.

Digital signature

Signed by APN LLC. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

TBNHlpr_x64_exe is a Windows file recorded in the ThreatInfo database. It is associated with APN Toolbar Notifier Helper. The reported company name is APN. The current detection status is Undefined, based on the latest analysis from 2025-02-07 23:01:33 (a year 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: APN Toolbar Notifier Helper
Company Name: APN
MD5: 97215c5841e988a436773e321515fa69
Size: 189 KB
First Published: 2017-05-21 07:08:26 (8 years ago)
Latest Published: 2025-02-07 23:01:33 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-02-07 23:01:33 (a year ago)
Signed By: APN LLC
Status: Valid

The signature on TBNHlpr_x64_exe 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%\archivos de programa\askpartnernetwork\toolbar\adap-tg\source\program files\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\ars2-tmg\source\program files\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\clmsoc-g\source\program files\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\real9-g\source\program files\askpartnernetwork\toolbar\updater
%system%\config\systemprofile\appdata\local\microsoft\windows\inetcache\ie\asktoolbarinstaller-orj-speepeijvop.7z\program files\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\avgsp2-sg\source\program files\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\vdj-sp\source\program files\askpartnernetwork\toolbar\updater
%system%\config\systemprofile\appdata\local\microsoft\windows\temporary internet files\content.ie5\asktoolbarinstaller-avira-v7ilf1oozh.7z\program files\askpartnernetwork\toolbar\updater
%programfiles%\askpartnernetwork\toolbar\sgtsp-sat\source\program files\askpartnernetwork\toolbar\updater

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

tbnhlpr_x64.exe A0244048.exe tbnhlpr_x64-d54f4802-17d1-4d54-b0a8-cbeb4288f823.exe A0154884.exe A0154980.exe A0154935.exe TBNHlpr_x64_exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 7 47.8%
Windows 10 29.5%
Windows 8.1 15.9%
Windows XP 3.2%
Windows 8 2.2%
Windows Vista 1.2%
Windows Small Business Server 2011 0.2%

The most common operating system signal for TBNHlpr_x64_exe is Windows 7 with 47.8% 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.

TBNHlpr_x64_exe 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 0x000079f8
Image base 0x0000000140000000

PE Sections:

Sections 6
Raw data 187392

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

.text 114176 bytes · 60.9% of section data
MD5 3e09476526c9c6fd632ddfcbec394283
.rdata 53248 bytes · 28.4% of section data
MD5 a79d11f97db7cea6af4ee02fa3766a77
.data 9216 bytes · 4.9% of section data
MD5 7bc46c96c28da265ff60d9f3ec4c9db1
.pdata 6656 bytes · 3.6% of section data
MD5 4e2ddb4e63a2183993c900b01b02d40a
.rsrc 1536 bytes · 0.8% of section data
MD5 27fcd4e04cb72500d52cfb73affc5de7
.reloc 2560 bytes · 1.4% of section data
MD5 f7d2b9ed02fe15286ee224b47b68642b

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 97215c5841e988a436773e321515fa69.
  • 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.