GridinSoft Threat Intelligence
node.exe threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. 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.Heur!
- Recommended action
- Scan and remove
- Last analysis
- 2026-05-26 06:00:18 (a day ago)
- File hash
- ad787c022c78a60c548ac9cedb0979f6
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Trojan.Heur!, part of the Trojan threat category.
Malware disguised as legitimate software or delivered through deceptive packaging. Related Trojan reports help compare this file with nearby detections, publishers, and hashes.
First seen 2026-05-26 06:00:18 (a day ago); latest analysis 2026-05-26 06:00:18 (a day ago).
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. Review the Trojan category for related samples and common context.
File context
node.exe is a Windows file recorded in the ThreatInfo database. It is associated with Node.js. The reported company name is Node.js. The current detection status is Trojan.Heur!, based on the latest analysis from 2026-05-26 06:00:18 (a day ago). ThreatInfo groups this verdict with Trojan reports for broader family-level investigation.
If node.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 Trojan.Heur!.
File Details
| Product Name: | Node.js |
| Company Name: | Node.js |
| MD5: | ad787c022c78a60c548ac9cedb0979f6 |
| Size: | 95 MB |
| First Published: | 2026-05-26 06:00:18 (a day ago) |
| Latest Published: | 2026-05-26 06:00:18 (a day ago) |
| Status: | Trojan.Heur! (on last analysis) | |
| Analysis Date: | 2026-05-26 06:00:18 (a day 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:
| %localappdata%\python\pythoncore-3.14-64\lib\site-packages |
| %localappdata%\programs\python\python311\lib\site-packages |
| %profile%\onedrive\documents\vs code\capstone\1-28 in class activity notebook\gen_ai_course_site_spring_2026-main\venv\lib\site-packages |
ThreatInfo has observed node.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 node.exe across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is French Polynesia with 100.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 node.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
node.exe is identified as pe for 64-bit systems. The subsystem is Windows CUI. 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.
b7ead51afe94d519af595da71af313a6
c3586170a198aabe23ab326d9efeeb54
5ab1c3b780e83aa205c6f12905721380
ea9e62a3dd92e4ba3cfad842702d70bf
bf619eac0cdf3f68d496ea9344137e8b
58a5ae98a1d4a0aa82770b5cd12b2161
8a1c755be27118356232a410ff9bad03
6a40e0e827d84945a11b632e81a68b7e
5cff913d72029e5fcd8cad78940fc7bb
326d7aa1b1fdf29b39faf6c623520a32
a7626a282907eca4576c17fee5390415
781af89929d904f16f9abf7d44ef8853
e44ea617d6d4f0f73403b9385497bc9b
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 Trojan.Heur!
This report identifies node.exe by MD5 ad787c022c78a60c548ac9cedb0979f6. It is part of the Trojan report group. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.