GridinSoft Threat Intelligence
nexus 2.exe threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Adware.OpenCandy. 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
- Adware.OpenCandy
- Recommended action
- Scan and remove
- Last analysis
- 2023-07-03 23:01:25 (2 years ago)
- File hash
- f7eab07881c292e598092aa4e8ab2587
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Adware.OpenCandy.
First seen 2023-02-19 23:01:26 (3 years ago); latest analysis 2023-07-03 23:01:25 (2 years ago).
Product metadata: AutoPlay Media Studio Launcher.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
nexus 2.exe is a Windows file recorded in the ThreatInfo database. It is associated with AutoPlay Media Studio Launcher. The current detection status is Adware.OpenCandy, based on the latest analysis from 2023-07-03 23:01:25 (2 years ago).
If nexus 2.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 Adware.OpenCandy.
File Details
| Product Name: | AutoPlay Media Studio Launcher |
| MD5: | f7eab07881c292e598092aa4e8ab2587 |
| Size: | 55 MB |
| First Published: | 2023-02-19 23:01:26 (3 years ago) |
| Latest Published: | 2023-07-03 23:01:25 (2 years ago) |
| Status: | Adware.OpenCandy (on last analysis) | |
| Analysis Date: | 2023-07-03 23:01:25 (2 years ago) |
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.
Common Places:
| %sysdrive% |
| %profile% |
ThreatInfo has observed nexus 2.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.
Geographic signal
Observed country distribution
ThreatInfo has seen nexus 2.exe across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Chile with 50.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for nexus 2.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.
Analysis
nexus 2.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
7a5f47e1f4e93c2c2497f288c72f6100
6b073044f9ac86118bb8f7b13a628b19
eb203a75f568d36a10bd99afd86be1ed
3675b5c1d6aa8d6919b67c2fd45fa7a0
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 Adware.OpenCandy
This report identifies nexus 2.exe by MD5 f7eab07881c292e598092aa4e8ab2587. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.