GridinSoft Threat Intelligence

libnut.node file report

Under review File reputation report
MD5 cd20c2b837f4a2f936211c58778bb394
Latest seen 2025-04-12 23:01:44 (a year ago)
First seen 2025-04-12 23:01:44 (a year ago)
Size 168 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2025-04-12 23:01:44 (a year ago); latest analysis 2025-04-12 23:01:44 (a year ago).

Digital signature

Signed by 上海哔哩哔哩科技有限公司. 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. 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.

libnut.node is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2025-04-12 23:01:44 (a year 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.

MD5: cd20c2b837f4a2f936211c58778bb394
Size: 168 KB
First Published: 2025-04-12 23:01:44 (a year ago)
Latest Published: 2025-04-12 23:01:44 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-04-12 23:01:44 (a year ago)
Signed By: 上海哔哩哔哩科技有限公司
Status: Valid

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

%programfiles%\bilibili\resources\app.asar.unpacked\node_modules\@nut-tree\libnut-win32\build

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

libnut.node 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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x0000a45c
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 160768

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

.text 94720 bytes · 58.9% of section data
MD5 377e8063dbbb495bcc32d62986c589de
.rdata 50176 bytes · 31.2% of section data
MD5 3f62c18a82da57d96799941304884405
.data 5632 bytes · 3.5% of section data
MD5 bdad3ac9f80b910713a9eaaab07b7281
.pdata 6656 bytes · 4.1% of section data
MD5 40d3daf9b2f90eeae0d8063147e18adc
_RDATA 512 bytes · 0.3% of section data
Uncommon name
MD5 632af1aad75edc6b1a94992cc1847102
.rsrc 512 bytes · 0.3% of section data
MD5 106eb1a5ed9fc911defec918b5086d48
.reloc 2560 bytes · 1.6% of section data
MD5 00acb6d1f1eda97679816e072ebb60e1

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