File scan report
Verdict Safe
Is package- lock. json safe? Yes, no threats found.
Zero engine detections on a package-lock.json file with no behavioural or external-intel signals.
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Treat as a clean package-lock.json file; no further action required unless the file is modified or sourced from an untrusted location.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website it came from.
Keep your security software and system 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 60 flagged
- Flagged 0
- No detection 60
- No result 14
- Code signing Not applicable
- Test run Not applicable
- First seen 3mo 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
The file is unsigned and with no sandbox, network, or file it created activity recorded.
The complete absence of malicious detections across major and smaller engines, combined with no sandbox verdicts or external-intel hits, indicates no malware indicators. The file type (package-lock.json) is a standard Node.js artifact that antivirus engines rarely flag. While the rare and classification and lack of signing history limit long-term reputation data, nothing in the payload suggests malicious intent or behaviour.
What We Detected
No test-file, hacking tool, or adware-PUA labels present.
Threat Behavior
No sandbox execution data, no contacted hosts or URLs, no files it created, and external intelligence sources (YARAify, CIRCL) returned no matches. The file shows no MITRE techniques or offensive behaviour patterns.
What To Do Now
The file can be treated as a standard package-lock.json artifact. If obtained from a trusted source, it poses no known security risk. Re-scan after any modifications or if the file is later executed in an unexpected context.
Where this verdict could be wrong1 caveat
- JSON package-lock files are not typically scanned by AV engines, so zero detections may simply indicate the file type falls outside normal malware signatures.
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 malicious engine detections
- No behavioural or network indicators
- No external intelligence matches
6 sources checked · 4 complete · 2 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 60 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 2 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
- Jul 10, 2026, 2:31 AM UTC
- SHA-256
518499bde396f1d93f028e985fb247f676216af3b6ef5394474c07bf8727bf6b- SHA-1
faf90b4225a9d12edcfcf111ff3e96c067ecbccf- MD5
27f0bc8838c9c2ed3eb9e00f29a5f621
About this file
package-lock.json is a JSON file of 319.1 kB.
- Type and size
- JSON · 319.1 kB
- Signer
- Not applicable
- First seen
- Jul 10, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (74) and how widely the file has been seen.
Show the technical evidenceChapter 04
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is package-lock.json safe?
What is package-lock.json?
How many antivirus engines detected package-lock.json?
What is the SHA-256 hash of package-lock.json?
Is it safe to open package-lock.json?
How up to date is this analysis of package-lock.json?
Community
Member reviews and reports for this exact file hash.