GridinSoft Threat Intelligence

N360Downloader (2).exe file report

Clean record File reputation report
MD5 e89b65d367821adaa4ebff22aee9ea56
Latest seen 2023-01-16 23:45:06 (3 years ago)
First seen 2020-07-23 17:40:24 (5 years ago)
Size 998 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2020-07-23 17:40:24 (5 years ago); latest analysis 2023-01-16 23:45:06 (3 years ago).

Publisher context

Company metadata: Symantec Corporation. Product metadata: Norton Download Manager.

Digital signature

Signed by Symantec Corporation. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

N360Downloader (2).exe is a Windows file recorded in the ThreatInfo database. It is associated with Norton Download Manager. The reported company name is Symantec Corporation. The current detection status is Clean, based on the latest analysis from 2023-01-16 23:45:06 (3 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: Norton Download Manager
Company Name: Symantec Corporation
MD5: e89b65d367821adaa4ebff22aee9ea56
Size: 998 KB
First Published: 2020-07-23 17:40:24 (5 years ago)
Latest Published: 2023-01-16 23:45:06 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-01-16 23:45:06 (3 years ago)
Signed By: Symantec Corporation
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%desktop%\data\all users\documents\norton
%mydoc%

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

100.0%

The strongest geographic signal for this file is United States 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 N360Downloader (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.

N360Downloader (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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00001000
Image base 0x00400000

PE Sections:

Sections 2
Raw data 1011200

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

.text 951808 bytes · 94.1% of section data
MD5 963eb7ead86bbe8d27673cf6178306fb
.rsrc 59392 bytes · 5.9% of section data
MD5 664769cec6018386f8cb65fa100c8004

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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