GridinSoft Threat Intelligence
buffering.js threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as General Threat. 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
- General Threat
- Recommended action
- Scan and remove
- Last analysis
- 2026-05-02 23:01:38 (3 weeks ago)
- File hash
- 97bdf1176073be1e792d0b5faa0c6ac0
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as General Threat.
First seen 2017-05-26 03:10:58 (9 years ago); latest analysis 2026-05-02 23:01:38 (3 weeks 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.
File context
buffering.js is a Windows file recorded in the ThreatInfo database. The current detection status is General Threat, based on the latest analysis from 2026-05-02 23:01:38 (3 weeks ago).
If buffering.js 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 General Threat.
File Details
| MD5: | 97bdf1176073be1e792d0b5faa0c6ac0 |
| Size: | 1 KB |
| First Published: | 2017-05-26 03:10:58 (9 years ago) |
| Latest Published: | 2026-05-02 23:01:38 (3 weeks ago) |
| Status: | General Threat (on last analysis) | |
| Analysis Date: | 2026-05-02 23:01:38 (3 weeks 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:
| %programfiles%\microsoft visual studio 14.0\common7\ide\extensions\microsoft\web tools\external\bower\node_modules\through\test |
| %localappdata%\popcorn time ce\node_modules\through\test |
| %commondir%\adobe\cep\extensions\com.pixelsquid.heroplayer\node_modules\react\node_modules\envify\node_modules\through\test |
| %programfiles%\unity\editor\data\resources\upm\node_modules\through\test |
| %localappdata%\gamejoltclient\node_modules\through\test |
| %appdata%\brackets\extensions\user\adobe.brackets.extract\node\v0.5.0\node_modules\through\test |
| %temp%\nw800_1522\node_modules\through\test |
| %temp%\nw5816_2931\node_modules\through\test |
| %programfiles%\autodesk\desktop connect\forever\node_modules\through\test |
| %programfiles%\adobe\adobe photoshop cs6 (64 bit)\plug-ins\io.zeplin.photoshop\node_modules\through\test |
ThreatInfo has observed buffering.js 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 buffering.js across 73 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 33.9% 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 buffering.js is Windows 10 with 72.7% 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
Report conclusion
GridinSoft detects this file as General Threat
This report identifies buffering.js by MD5 97bdf1176073be1e792d0b5faa0c6ac0. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.