TCS.exe threat report

MD5 9048ee6457dff78a3de0104dd923a06c
Latest seen 2024-04-17 23:01:56 (2 years ago)
First seen 2024-04-17 23:01:56 (2 years ago)
Size 146 MB
Publisher ByteDance Inc
Product TCS
Signed by TIKTOK INC.

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2024-04-17 23:01:56 (2 years ago)
File hash
9048ee6457dff78a3de0104dd923a06c
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2024-04-17 23:01:56 (2 years ago); latest analysis 2024-04-17 23:01:56 (2 years ago).

Publisher context

Company metadata: ByteDance Inc. Product metadata: TCS.

Digital signature

Signed by TIKTOK 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. 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.

TCS.exe is a Windows file recorded in the ThreatInfo database. It is associated with TCS. The reported company name is ByteDance Inc. The current detection status is Trojan.Heur!, based on the latest analysis from 2024-04-17 23:01:56 (2 years ago).

If TCS.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 Trojan.Heur!.

Product Name: TCS
Company Name: ByteDance Inc
MD5: 9048ee6457dff78a3de0104dd923a06c
Size: 146 MB
First Published: 2024-04-17 23:01:56 (2 years ago)
Latest Published: 2024-04-17 23:01:56 (2 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2024-04-17 23:01:56 (2 years ago)
TCS.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: TIKTOK INC.
Status: Valid

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

%localappdata%\programs

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

100.0%

The strongest geographic signal for this file is Germany with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for TCS.exe 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.

TCS.exe is identified as pe for 64 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x03ee8750

PE Sections:

Name Size of data MD5
.text 125003776 169280119107f2a1ee3d62d5c1b28f0f
.rdata 23233024 f21c0b745cd9b54e9bc9f967f206393e
.data 550400 9afe0fb2df24c26579647ca3fbcd61a0
.pdata 3968512 86fa4e4b0eea4e85542caeab811a5285
.00cfg 512 a11d902eb2ac7d2500fd17495d664c64
.gxfg 16896 22b32522d8f57aa284181e9637b791e2
.retplne 512 d71c80853fa92a73d6e7b213fb3fe5de
.rodata 5120 fc4989a94aa74cb7f83f987c76ee9418
.tls 1024 44a2fe445fb290522a2e3fbeb424a1c2
.voltbl 512 0ddb0dccb6bd5557c62a765efaac18be
CPADinfo 512 60d3ea61d541c9be2e845d2787fb9574
_RDATA 512 e0da1de0e938ba2ae2585f3034dd062d
malloc_h 512 fd13d12bc0550a2b3bca98128a2c18dc
.rsrc 221696 3f3d4be3abd29aef65a83236a721cfa6
.reloc 977408 79105f1ba65759880131405515ff6ec8

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.

More information: