GridinSoft Threat Intelligence

Au_.exe file report

Under review File reputation report
MD5 548ab37a1d34034e82f5b4f9096c63e2
Latest seen 2024-05-30 23:02:47 (2 years ago)
First seen 2017-05-31 14:14:35 (8 years ago)
Size 4 MB
Publisher SweetLabs,Inc.
Product Pokki
Signed by Pokki

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-31 14:14:35 (8 years ago); latest analysis 2024-05-30 23:02:47 (2 years ago).

Publisher context

Company metadata: SweetLabs,Inc.. Product metadata: Pokki.

Digital signature

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

Au_.exe is a Windows file recorded in the ThreatInfo database. It is associated with Pokki. The reported company name is SweetLabs,Inc.. The current detection status is Undefined, based on the latest analysis from 2024-05-30 23:02:47 (2 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: Pokki
Company Name: SweetLabs,Inc.
MD5: 548ab37a1d34034e82f5b4f9096c63e2
Size: 4 MB
First Published: 2017-05-31 14:14:35 (8 years ago)
Latest Published: 2024-05-30 23:02:47 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-30 23:02:47 (2 years ago)
Signed By: Pokki
Status: Valid

The signature on Au_.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%\sweetlabs app platform
%sysdrive%\adwcleaner\quarantine\files\grjbmbtjndckembuinevawqgcrxxqxzs
%temp%\~nsu.tmp
%sysdrive%\adwcleaner\quarantine\files\jfncslnevsrzxhtavqnnmkouaeecbnje
%sysdrive%\adwcleaner\quarantine\files\dapmgydgnrrakeruzkdgyzgcpdhfsddn
%sysdrive%\adwcleaner\quarantine\fraqbc8wsa
%sysdrive%\windows.old\users\артем\appdata\local\sweetlabs app platform
%sysdrive%\windows.old\users\jürgen\appdata\local\sweetlabs app platform
%temp%
%localappdata%

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

Uninstall.exe Cu_.exe Du_.exe Bu_.exe Au_.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 8.1 60.5%
Windows 10 39.5%

The most common operating system signal for Au_.exe is Windows 8.1 with 60.5% 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.

Au_.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 0x000038af
Image base 0x00400000

PE Sections:

Sections 6
Raw data 96768

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

.text 29696 bytes · 30.7% of section data
MD5 419d4e1be1ac35a5db9c47f553b27cea
.rdata 11264 bytes · 11.6% of section data
MD5 cca1ca3fbf99570f6de9b43ce767f368
.data 512 bytes · 0.5% of section data
MD5 77f0839f8ebea31040e462523e1c770e
.ndata 0 bytes · 0.0% of section data
Uncommon name
MD5 00000000000000000000000000000000
.rsrc 51200 bytes · 52.9% of section data
MD5 ade5b03af1f46176b5a56e99d4225adb
.reloc 4096 bytes · 4.2% of section data
MD5 a1aa9ef6a982ef1d93ec373edf867a30

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 548ab37a1d34034e82f5b4f9096c63e2.
  • 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.