GridinSoft Threat Intelligence

AsInvoker.exe file report

Under review File reputation report
MD5 c72ad4de70541c821526cafc47e2fc1d
Latest seen 2021-04-27 20:58:00 (5 years ago)
First seen 2021-04-27 20:58:00 (5 years ago)
Size 488 KB
Publisher Systweak Software.
Product Disk Speedup

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-04-27 20:58:00 (5 years ago); latest analysis 2021-04-27 20:58:00 (5 years ago).

Publisher context

Company metadata: Systweak Software.. Product metadata: Disk Speedup.

Digital signature

Signed by SYSTWEAK SOFTWARE PVT. LTD.. 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.

AsInvoker.exe is a Windows file recorded in the ThreatInfo database. It is associated with Disk Speedup. The reported company name is Systweak Software.. The current detection status is Undefined, based on the latest analysis from 2021-04-27 20:58:00 (5 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: Disk Speedup
Company Name: Systweak Software.
MD5: c72ad4de70541c821526cafc47e2fc1d
Size: 488 KB
First Published: 2021-04-27 20:58:00 (5 years ago)
Latest Published: 2021-04-27 20:58:00 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-04-27 20:58:00 (5 years ago)
Signed By: SYSTWEAK SOFTWARE PVT. LTD.
Status: Valid

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

%programfiles%

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

Windows 10 100.0%

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

AsInvoker.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 0x00002954
Image base 0x00400000

PE Sections:

Sections 4
Raw data 493056

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

.text 35840 bytes · 7.3% of section data
MD5 bb805697579dc9a829313036ac88bdc2
.rdata 10240 bytes · 2.1% of section data
MD5 a0bc7a858cdb0cd904d44dfb744851e3
.data 3584 bytes · 0.7% of section data
MD5 823ace2a8e701019d3d3bc5d4c5e0d22
.rsrc 443392 bytes · 89.9% of section data
MD5 6e0266e42de3e67e1edd6a72d7e179af

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 c72ad4de70541c821526cafc47e2fc1d.
  • 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.