File scan report
Verdict Safe
Is common.
Zero detections across 76 engines and no malicious sandbox signals despite one rule-based flag.
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
No action required; the file presents no observable malicious indicators.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 62 flagged
- Flagged 0
- No detection 62
- No result 14
- Code signing Not applicable
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
0 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 62 antivirus engines that checked it returned clean. Sandbox showed no malicious verdict and no offensive techniques.
The file is a JavaScript bundle with zero malicious detections from any engine tier. Sandbox execution produced only techniques common in legitimate software and no malicious verdict. The credential-dumper rule-based 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 techniques common in legitimate software and no offensive MITRE activity. One rule-based rule fired on observed access to the Windows password store, but the file type and lack of corroborating signals make this likely sandbox noise.
Threat Behavior
No control-server domains, dropped malicious files it created, or persistence mechanisms were identified. The single file it created remains unclassified and shows no malicious indicators.
What To Do Now
The file can be treated as benign. Keep security software enabled and continue normal security practices.
- Zero engine detections across all tiers
- No malicious sandbox verdict
- No external intelligence hits
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 4sandbox rule tags
- 2spawned processes
- 0network contacts
- 6filesystem & mutex artifacts
Includes 4 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
None of the 62 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Aug 27, 2026, 2:48 PM UTC
- SHA-256
69ed399785761bab847a393350da9a78b47c1c54d7e3f7ce5a4b4cce41ac919f- SHA-1
fb5fb319634f6b7d3f49c3b9f776accec1b31254- MD5
46430f0e910ee7cda5acb322abec6d72
About this file
common.bundle.js is a JavaScript file of 890.1 kB.
- Type and size
- JavaScript · 890.1 kB
- Signer
- Not applicable
- First seen
- Aug 29, 2025On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (76) and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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.