GridinSoft Threat Intelligence

node.dll file report

Under review File reputation report
MD5 51bee474208f9c531c9c59d23759b5b5
Latest seen 2026-05-06 23:01:58 (2 weeks ago)
First seen 2022-09-28 23:58:00 (3 years ago)
Size 11 MB
Product nwjs

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2022-09-28 23:58:00 (3 years ago); latest analysis 2026-05-06 23:01:58 (2 weeks ago).

Publisher context

Company metadata: The NW.js Community. Product metadata: nwjs.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

node.dll is a Windows file recorded in the ThreatInfo database. It is associated with nwjs. The reported company name is The NW.js Community. The current detection status is Undefined, based on the latest analysis from 2026-05-06 23:01:58 (2 weeks ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: nwjs
Company Name: The NW.js Community
MD5: 51bee474208f9c531c9c59d23759b5b5
Size: 11 MB
First Published: 2022-09-28 23:58:00 (3 years ago)
Latest Published: 2026-05-06 23:01:58 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-05-06 23:01:58 (2 weeks ago)
%profile%\pcappstore
%programfiles%\pcappstore

ThreatInfo has observed node.dll 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.

Windows 10 100.0%

The most common operating system signal for node.dll 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.

node.dll 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 0x005d51ed
Image base 0x10000000

PE Sections:

Sections 8
Raw data 12164608

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

.text 6517760 bytes · 53.6% of section data
Large raw data
MD5 5bcce7a4720152d03f75ec5b32a862b1
.rdata 5304320 bytes · 43.6% of section data
Large raw data
MD5 c1153442a0449d0214c2d8219aff67e1
.data 30208 bytes · 0.2% of section data
MD5 a9349128ec02ce7f3eeb9224ca5d6a86
.00cfg 512 bytes · 0.0% of section data
Uncommon name
MD5 9db8ce88e5399c4892c33e276faecec2
.tls 512 bytes · 0.0% of section data
MD5 134b5956ca7a32f7432044b77c8438ef
.voltbl 1024 bytes · 0.0% of section data
Uncommon name
MD5 906dbc81f38538ba292a15d769e58ad4
.rsrc 1536 bytes · 0.0% of section data
MD5 75a4c04d740e4456f5888d71a574a2ab
.reloc 308736 bytes · 2.5% of section data
MD5 ac66998cfd8f56fff04ab3ed36f53e3f

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 51bee474208f9c531c9c59d23759b5b5.
  • 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.