GridinSoft Threat Intelligence

node-quarantine.node file report

Under review File reputation report
MD5 e71c76feeea89ba2f99e2d67c68d2a03
Latest seen 2021-07-10 20:38:19 (4 years ago)
First seen 2021-07-09 20:13:10 (4 years ago)
Size 96 KB
Signed by WhatsApp, Inc

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-07-09 20:13:10 (4 years ago); latest analysis 2021-07-10 20:38:19 (4 years ago).

Digital signature

Signed by WhatsApp, Inc. 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.

node-quarantine.node is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2021-07-10 20:38:19 (4 years 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: e71c76feeea89ba2f99e2d67c68d2a03
Size: 96 KB
First Published: 2021-07-09 20:13:10 (4 years ago)
Latest Published: 2021-07-10 20:38:19 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-07-10 20:38:19 (4 years ago)
Signed By: WhatsApp, Inc
Status: Valid

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

%localappdata%\whatsapp\app-2.2123.7\resources\app.asar.unpacked\node_modules\node-quarantine\bin

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

node-quarantine.node is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00001364
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 88576

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

.text 44544 bytes · 50.3% of section data
MD5 d35d56c6c67b8c23b4f27fabd220e024
.rdata 35328 bytes · 39.9% of section data
MD5 975a6db242a23986c503326f31366b24
.data 2560 bytes · 2.9% of section data
MD5 a6bdf8e6b8f8f103201c634461d2d7aa
.pdata 3584 bytes · 4.0% of section data
MD5 7d47ad9e0d567cfea6b31c0ce4d567ef
.rsrc 512 bytes · 0.6% of section data
MD5 c7a4e8ec050a078d37fff5197af953e2
.reloc 2048 bytes · 2.3% of section data
MD5 10723a516357dbd55fd17ed50dff1bb2

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