GridinSoft Threat Intelligence

bitcomet_setup[2].exe threat report

Detected as Adware.InstallCore File reputation report
MD5 59fdc387f79f78b5d0dd6cc6f44ce20b
Latest seen 2024-08-17 23:00:39 (2 years ago)
First seen 2018-08-07 20:09:18 (7 years ago)
Size 1 MB
Publisher
Product Rigohikene
Signed by Xing Wang

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Adware.InstallCore. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Adware.InstallCore
Recommended action
Scan and remove
Last analysis
2024-08-17 23:00:39 (2 years ago)
File hash
59fdc387f79f78b5d0dd6cc6f44ce20b
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Adware.InstallCore, part of the Adware threat category.

Category context

Programs that inject advertising, change browser behavior, or monetize traffic through bundled components. Related Adware reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2018-08-07 20:09:18 (7 years ago); latest analysis 2024-08-17 23:00:39 (2 years ago).

Publisher context

Company metadata: . Product metadata: Rigohikene .

Digital signature

Signed by Xing Wang. 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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present. Review the Adware category for related samples and common context.

bitcomet_setup[2].exe is a Windows file recorded in the ThreatInfo database. It is associated with Rigohikene . The reported company name is . The current detection status is Adware.InstallCore, based on the latest analysis from 2024-08-17 23:00:39 (2 years ago). ThreatInfo groups this verdict with Adware reports for broader family-level investigation.

If bitcomet_setup[2].exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Adware.InstallCore.

Product Name: Rigohikene
Company Name:
MD5: 59fdc387f79f78b5d0dd6cc6f44ce20b
Size: 1 MB
First Published: 2018-08-07 20:09:18 (7 years ago)
Latest Published: 2024-08-17 23:00:39 (2 years ago)
Status: Adware.InstallCore (on last analysis)
Analysis Date: 2024-08-17 23:00:39 (2 years ago)
bitcomet_setup[2].exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: Xing Wang
Status: Valid

The signature on bitcomet_setup[2].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.

%temp%
%profile%
%localappdata%\microsoft\windows\inetcache\ie
%profile%\downloads
%sysdrive%\owner files
%localappdata%\microsoft\windows\temporary internet files\content.ie5
%sysdrive%
%sysdrive%\gereksizler
%localappdata%\packages\microsoft.microsoftedge_8wekyb3d8bbwe\tempstate
%localappdata%\packages\microsoft.microsoftedge_8wekyb3d8bbwe\ac\#!001\microsoftedge\cache

ThreatInfo has observed bitcomet_setup[2].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.

Bit3B7E.tmp.exe bitcomet_setup.exe Bit1C72.tmp.exe BitF39.tmp.exe bitcomet_setup[1].exe Bit97FA.tmp.exe Bit5F9C.tmp.exe Bit5998.tmp.exe Bit5587.tmp.exe BitC995.tmp.exe Bit970F.tmp.exe Bit6545.tmp.exe Bit661F.tmp.exe Bit5678.tmp.exe BitF887.tmp.exe BitC2B9.tmp.exe BitB76C.tmp.exe Bit44E7.tmp.exe Bit222.tmp.exe Bit895F.tmp.exe bitcomet_setup (2).exe bitcomet_setup (3).exe bitcomet_setup (1).exe Bit7355.tmp.exe Bit230C.tmp.exe Bit4BB.tmp.exe BitD80B.tmp.exe 3bitcomet_setup.exe Bit569E.tmp.exe BitC405.tmp.exe Bit57F.tmp.exe Bit2825.tmp.exe BitAEBF.tmp.exe Bit67EB.tmp.exe BitB0B9.tmp.exe bitcomet_setup[4].exe bitcomet_setup[3].exe Bit49E3.tmp.exe BitF895.tmp.exe BitFD2B.tmp.exe BitE9E5.tmp.exe Bit26C2.tmp.exe Bit6430.tmp.exe BitFBF1.tmp.exe Bit3485.tmp.exe Bit3292.tmp.exe BitCA28.tmp.exe BitB948.tmp.exe Bit58C.tmp.exe Bit7030.tmp.exe BitD146.tmp.exe BitA9A.tmp.exe BitB5DC.tmp.exe Bit312.tmp.exe Bit5ED6.tmp.exe Bit3B22.tmp.exe BitA69D.tmp.exe Bit645D.tmp.exe Bit3A03.tmp.exe BitCA12.tmp.exe BitF3A4.tmp.exe Bit4A23.tmp.exe BitC2A9.tmp.exe Bit9896.tmp.exe Bit1111.tmp.exe Bit9C59.tmp.exe Bit76B5.tmp.exe Bit2AF.tmp.exe BitAD92.tmp.exe Bit465C.tmp.exe Bit76D.tmp.exe Bit2DFF.tmp.exe Bit1652.tmp.exe Bit9AEE.tmp.exe BitEF27.tmp.exe Bit1D1C.tmp.exe BitEEE.tmp.exe Bit2F67.tmp.exe BitF8EE.tmp.exe BitCBC6.tmp.exe Bit9E12.tmp.exe Bit580E.tmp.exe Bit27CD.tmp.exe Bit457E.tmp.exe BitC2A5.tmp.exe BitC654.tmp.exe Bit6641.tmp.exe Bit64D8.tmp.exe BitEFE9.tmp.exe Bit4059.tmp.exe Bit32E2.tmp.exe BitCCF4.tmp.exe Bit279F.tmp.exe Bit6B01.tmp.exe Bit2A3B.tmp.exe Bit4DF1.tmp.exe Bit8FD3.tmp.exe bitcomet_setup[2].exe BitC89B.tmp.exe BitA0D0.tmp.exe BitEF10.tmp.exe BitF68E.tmp.exe Bit96C4.tmp.exe Bit560B.tmp.exe Bit4588.tmp.exe BitBDD2.tmp.exe Bit2A83.tmp.exe BitEEB5.tmp.exe BitE13A.tmp.exe Bit3DCD.tmp.exe Bit1FB1.tmp.exe BitFF06.tmp.exe BitEBC9.tmp.exe BitAB30.tmp.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 55.1%
Windows 10 32.8%
Windows 8.1 9.4%
Windows Vista 2.3%
Windows 8 0.4%

The most common operating system signal for bitcomet_setup[2].exe is Windows 7 with 55.1% 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.

bitcomet_setup[2].exe 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 0x0000a5f8
Image base 0x00400000

PE Sections:

Sections 8
Raw data 104960

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

CODE 40448 bytes · 38.5% of section data
MD5 9b6bbb3cc75e0b30b67a89e082ebc1e1
DATA 1024 bytes · 1.0% of section data
MD5 beee52f18301950f82460d9ffe5aec7e
BSS 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.idata 2560 bytes · 2.4% of section data
MD5 bb5485bf968b970e5ea81292af2acdba
.tls 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.rdata 512 bytes · 0.5% of section data
MD5 9ba824905bf9c7922b6fc87a38b74366
.reloc 0 bytes · 0.0% of section data
MD5 00000000000000000000000000000000
.rsrc 60416 bytes · 57.6% of section data
MD5 738a81b63dafe66367ea16d524240247

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

GridinSoft detects this file as Adware.InstallCore

This report identifies bitcomet_setup[2].exe by MD5 59fdc387f79f78b5d0dd6cc6f44ce20b. It is part of the Adware report group. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 59fdc387f79f78b5d0dd6cc6f44ce20b.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found. Use the Adware category to compare similar reports.