Imba threat report

MD5 726ea24c1f46d883a40bd59215cd26df
Latest seen 2023-03-31 23:52:31 (3 years ago)
First seen 2023-03-31 23:52:31 (3 years ago)
Size 4 MB
Product Imba
Signed by 10700

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Kryptik. 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.Kryptik
Recommended action
Scan and remove
Last analysis
2023-03-31 23:52:31 (3 years ago)
File hash
726ea24c1f46d883a40bd59215cd26df
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Kryptik.

Timeline

First seen 2023-03-31 23:52:31 (3 years ago); latest analysis 2023-03-31 23:52:31 (3 years ago).

Publisher context

Product metadata: Imba.

Digital signature

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

Imba is a Windows file recorded in the ThreatInfo database. It is associated with Imba. The current detection status is Trojan.Kryptik, based on the latest analysis from 2023-03-31 23:52:31 (3 years ago).

If Imba 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.Kryptik.

Product Name: Imba
MD5: 726ea24c1f46d883a40bd59215cd26df
Size: 4 MB
First Published: 2023-03-31 23:52:31 (3 years ago)
Latest Published: 2023-03-31 23:52:31 (3 years ago)
Status: Trojan.Kryptik (on last analysis)
Analysis Date: 2023-03-31 23:52:31 (3 years ago)
Imba 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: 10700
Status: Valid

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

%sysdrive%\windows.old\users\flia. mejia vergara\appdata\local\microsoft\windows\inetcache\ie

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

Imba is identified as pe for 32 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: 32
Image Base: 0x00400000
Entry Address: 0x00008693

PE Sections:

Name Size of data MD5
.text 4213248 734dba980a49cfe20e726a7496862f42
.data 12288 dd897c347d32f9c0da7975b5199ec778
.rsrc 30208 be80d3081b2f6a4fca9a3fe8d73698b6
.reloc 25088 bf55ca78963ebc9fb25efab2c9ef3f43

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: