MalwareTips

File scan report

Scan another file

Verdict Safe

Analyzed , 3 days ago

Is package.json safe? Yes, no threats found.

A small 1642-byte JSON data file named package.json that none of the 59 antivirus engines that checked it flagged, with no external database hits and no hostile indicators.

Read the whole reasonShow less

Moderate evidence · No engine flags it, but no publisher signature confirms who made it.

Open it as usual if it came from the official source

The file looks safe to use as a data file. If it is a project manifest from an untrusted source, check its script entries before running an install.

Good practice2 tips

We found nothing harmful in this file.

  1. Open it only if you trust the person or website it came from.

  2. Keep your security software and system updates switched on.

No scanner can promise a file is 100% safe.

Why we think so

Share this file report

package.json: Safe — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Antivirus results

0 of 59 flagged

  • Flagged 0
  • No detection 59
  • No result 16
Filepackage.json1.6 kBSHA-256 e0436a5cd8a1…8a3054
  • Code signing Not applicable
  • Test run Not applicable
  • First seen 3d ago
No sandbox test run results are available for this file.

Chapter 02

Why we think so

1 point against it and 4 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

No MalwareBazaar, YARA or reference-database hits were found. Nothing in the evidence points to hostile content, though the file is rarely submitted.

Where this verdict could be wrong1 caveat
  • The file is rarely submitted (1 submitter) and first seen on Oct 22, 2026, so reputation history is thin; a package.json can carry install scripts, and its contents were not statically analysed by us.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

6 sources checked · 4 complete · 2 not needed or not applicable. See every source

Chapter 03

Technical details

None of the 59 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompletePositive signal: 0 of 59 engines flagged it · 16 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesNot applicableSandboxes do not run this kind of fileNo date recorded
Contacted hostsMalwareTips URL scannerNot neededNo sandbox run, so there were no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesCompleteNo rule matched
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

File fingerprint

Last analyzed
Oct 23, 2026, 12:58 PM UTC
SHA-256
e0436a5cd8a1f380e3ae23eafe13eb7f4ed87d1c7af5449e8b859954f38a3054
SHA-1
bc9775f8776aa018c4a2741ebdbb1addb9103361
MD5
9318ee5d46010a1f3ecf288fdd27c939

About this file

package.json is a JSON file of 1.6 kB.

Type and size
JSON · 1.6 kB
Signer
Not applicable
First seen
Oct 22, 2026On VirusTotal.
Submitted by
1 sourceRarely seen: few people have submitted this exact file.

First scanned

Chapter 04

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is package.json safe?
We found nothing harmful in package.json. None of the 59 antivirus engines that checked it flag it. Open it only if you trust the person or website it came from.
What is package.json?
package.json is a file, about 1.6 kB. VirusTotal first saw it on Oct 22, 2026.
How many antivirus engines detected package.json?
None of the 59 antivirus engines that checked it flag package.json. That is a good sign, but not proof, so we also weigh who made it, how widely it is used and what it did in a test run.
What is the SHA-256 hash of package.json?
The SHA-256 fingerprint of package.json is e0436a5cd8a1f380e3ae23eafe13eb7f4ed87d1c7af5449e8b859954f38a3054, and its MD5 is 9318ee5d46010a1f3ecf288fdd27c939. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
Is it safe to open package.json?
We found nothing harmful in package.json. The main caveat is where you got it: attackers sometimes spread malware under the name of real software, so get it from the official website. If your own antivirus warns about it, check the source before you ignore the warning.
How up to date is this analysis of package.json?
This report reflects the scan on Oct 23, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.