GridinSoft Threat Intelligence

AutoPico(1).exe threat report

Detected as Possible Threat File reputation report
MD5 cfe1c391464c446099a5eb33276f6d57
Latest seen 2025-02-21 23:00:57 (a year ago)
First seen 2017-05-21 06:07:21 (8 years ago)
Size 728 KB
Publisher @ByELDI
Product AutoPico
Signed by @ByELDI

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Possible Threat. 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
Possible Threat
Recommended action
Scan and remove
Last analysis
2025-02-21 23:00:57 (a year ago)
File hash
cfe1c391464c446099a5eb33276f6d57
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Possible Threat.

Timeline

First seen 2017-05-21 06:07:21 (8 years ago); latest analysis 2025-02-21 23:00:57 (a year ago).

Publisher context

Company metadata: @ByELDI. Product metadata: AutoPico.

Digital signature

Signed by @ByELDI. 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.

AutoPico(1).exe is a Windows file recorded in the ThreatInfo database. It is associated with AutoPico. The reported company name is @ByELDI. The current detection status is Possible Threat, based on the latest analysis from 2025-02-21 23:00:57 (a year ago).

If AutoPico(1).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 Possible Threat.

Product Name: AutoPico
Company Name: @ByELDI
MD5: cfe1c391464c446099a5eb33276f6d57
Size: 728 KB
First Published: 2017-05-21 06:07:21 (8 years ago)
Latest Published: 2025-02-21 23:00:57 (a year ago)
Status: Possible Threat (on last analysis)
Analysis Date: 2025-02-21 23:00:57 (a year ago)
AutoPico(1).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: @ByELDI
Status: Valid

The signature on AutoPico(1).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%\kmspico
%desktop%\kmspico 10.2 final by gdaily\kmspico 10.2 final\kmspico portable
%temp%\rar$exa0.516\bkshare.com-kmspico 10.2.0\kmspico portable
%temp%\kmspico
%profile%\downloads\win10.vn - kmspico_v10.2.0_portable\win10.vn - kmspico_v10.2.0_portable
%appdata%\zhp\quarantine\kmspico portable\kmspico portable
%sysdrive%\activators\kmspico v10.2.0 portable
%mydoc%\kmspico portable
%desktop%\tool\kmspico portable v10.2.0 final\kmspico portable
%profile%\downloads\[phanmemaz.com].kmspico 10.2.0\kmspico portable

ThreatInfo has observed AutoPico(1).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.

AutoPico.exe vAutoPico.exe Sauveur.exe AutoPico (1).exe AutoPico (2017_08_10 13_53_02 UTC).exe AutoPico (2017_09_11 13_07_55 UTC).exe gAutoPico.exe AutoPico(1).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 10 69.7%
Windows 7 18.0%
Windows 8.1 10.5%
Windows 8 1.2%
Windows XP 0.4%
Windows Vista 0.1%
Windows Server 2012 0.1%
Windows Embedded 8.1 0.1%

The most common operating system signal for AutoPico(1).exe is Windows 10 with 69.7% 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.

AutoPico(1).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 0x000b5ade
Image base 0x00400000

.NET Info:

MVID: 5be50f82-ede8-414a-aa1c-a062fd26a496

PE Sections:

Sections 3
Raw data 740864

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

.text 736256 bytes · 99.4% of section data
MD5 149bcf24f1dc280bf094d79d8fa30752
.rsrc 4096 bytes · 0.6% of section data
MD5 e489e8d4908f8e684f5aab6b28497c7a
.reloc 512 bytes · 0.1% of section data
MD5 dc3629355267911f132493f301a315e2

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 Possible Threat

This report identifies AutoPico(1).exe by MD5 cfe1c391464c446099a5eb33276f6d57. 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 cfe1c391464c446099a5eb33276f6d57.
  • 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.