Is common.bundle.js safe?
Zero detections across 76 engines and no malicious sandbox signals despite one heuristic flag.
All 76 engines returned clean. Sandbox showed no malicious verdict and no offensive techniques. The single heuristic on LSASS access is inconsistent with a JavaScript file and lacks corroboration.
69ed399785761bab84…4b4cce41ac919fRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 76 engines returned clean. Sandbox showed no malicious verdict and no offensive techniques. The single heuristic on LSASS access is inconsistent with a JavaScript file and lacks corroboration.
The file is a 364-day-old JavaScript bundle with zero malicious detections from any engine tier. Sandbox execution produced only ambient techniques and no malicious verdict. The credential-dumper heuristic appears to be sandbox noise given the file type and absence of offensive MITRE indicators. No external intelligence or similar-hash matches exist to contradict the clean result.
What We Detected
76 engines scanned the JavaScript file; none flagged it malicious or suspicious. Sandbox execution recorded four ambient techniques and no offensive MITRE activity. One heuristic rule fired on observed LSASS process access, but the file type and lack of corroborating signals make this likely sandbox noise.
Threat Behavior
No C2 domains, dropped malicious children, or persistence mechanisms were identified. The single dropped child remains unclassified and shows no malicious indicators.
What To Do Now
The file can be treated as benign. Keep endpoint protection enabled and continue normal security practices.
Where this verdict could be wrong1 caveat
- triggeredHeuristics reports LSASS access, but fileType=JavaScript and sandboxVerdicts empty — heuristic may be sandbox noise or mis-attribution.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero engine detections across all tiers
- No malicious sandbox verdict
- No external intelligence hits
No action required; the file presents no observable malicious indicators.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 4MITRE ATT&CK techniques
- 9spawned processes
- 0network contacts
- 6filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
common.bundle.js
69ed399785761bab847a393350da9a78b47c1c54d7e3f7ce5a4b4cce41ac919f
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\common.bundle.js"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis - Written fileObserved
Logs
C:\ProgramData\Microsoft\Windows Security Health\Logs
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\ProgramData\Microsoft\Windows Security Health\Logs
- \BaseNamedObjects\Local\SM0:6900:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:6900:120:WilError_03
- \BaseNamedObjects\Local\ZonesCacheCounterMutex
- \BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- 000cb99c15e0ed813e4e…a7138cNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 76engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 76 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: common.bundle.js — 69ed399785761bab847a393350da9a78b47c1c54d7e3f7ce5a4b4cce41ac919f
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Windows\system32\wscript.exe" "C:\Users\<USER>\Desktop\common.bundle.js"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Logs — C:\ProgramData\Microsoft\Windows Security Health\Logs
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
0 of 76 engines flagged this file
View all 76 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Rarely uploaded, but has been around for a while. Often niche legitimate software or old internal tooling; not a strong malware signal on its own.
Fingerprint and provenance
- File name
- common.bundle.js
- Format
- JavaScript
- Code signing
- Not applicable to this file type
- Size
- 869.2 KB
- Last analyzed
- Aug 27, 2026, 2:48 PM UTC
69ed399785761bab847a393350da9a78b47c1c54d7e3f7ce5a4b4cce41ac919fSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is common.bundle.js safe?
What is common.bundle.js?
How many antivirus engines detected common.bundle.js?
What is the SHA-256 hash of common.bundle.js?
Is it safe to run common.bundle.js?
How up to date is this analysis of common.bundle.js?
Community
Member reviews and reports for this exact file hash.