File scan report
Verdict Safe
Is LJSONedit.
None of the 70 antivirus engines that checked it flagged this unsigned JSON editor executable, and the combined sandbox verdict was clean with no high-risk techniques recorded.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The file appears safe to use. Obtain it from the developer's official source and keep your security software enabled.
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.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen Today
Chapter 02
Why we think so
2 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The combined sandbox verdict was clean, and the file shows no packing. It is unsigned and rarely submitted, first seen on Oct 26, 2026, so download it only from the developer's own site.
No engine reported a detection, and all 18 major antivirus engines returned clean results. The combined sandbox verdict over three runs was clean, and no high-risk techniques or injected processes were recorded. The sandbox did not record the sample making any network connections. The antivirus analysis found no packer and normal code entropy. Against this, the file is unsigned and has been seen from only two sources, so there is no publisher history to vouch for it.
What We Detected
None of the 70 antivirus engines that checked it flagged this 64-bit Windows executable, and all 18 major antivirus engines reported it clean. It does not match any public malware database or community malware rule. The antivirus analysis found no packer, and the code entropy is normal.
Threat Behavior
Three sandbox runs produced a combined clean verdict. They recorded only techniques common in legitimate software, with no injected processes, no persistence and no network contacts from the sample. The file is unsigned, was first seen on Oct 26, 2026 and has been submitted by only two sources.
What To Do Now
The evidence does not point to a threat. Because the program has no publisher signature and little history, download it from the developer's official page and keep your antivirus enabled.
Where this verdict could be wrong2 caveats
- The file is unsigned and was submitted by only two sources, so there is no publisher or wide-distribution history to confirm where it came from.
- Fresh malware can go undetected by engines at first, and no host-reputation check of network activity is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 70 antivirus engines that checked it flagged the file, including all 18 major antivirus engines.
- The combined sandbox verdict was clean, with no high-risk techniques recorded.
- No packing or unusual code entropy was found.
- There are no matches in public malware databases or community malware rules.
- The executable has no code signature.
- Few sources have submitted this file, and it was first seen on Oct 26, 2026.
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 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 8sandbox rule tags
- 2spawned processes
- 0network contacts
- 0filesystem & mutex artifacts
Includes the sandbox verdicts, 8 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 70 antivirus engines that checked it flag it; no publisher signature.
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
- Oct 26, 2026, 10:02 PM UTC
- SHA-256
33bdfdb25fa0b04cd2e2a85538763d97669c6106c625ac99115c7243b6a0cfd0- SHA-1
bdc71aee79b9a33189c30ccfd6e27cb260d1ad0d- MD5
2f8e24a40db9c951c32850861feae3a7
About this file
LJSONedit.exe says it is JSON editor (LJSONedit), 4.9 MB.
- Claims to be
- JSON editor (LJSONedit)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 4.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 26, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 5.61 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers 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 LJSONedit.exe safe?
What is LJSONedit.exe?
How many antivirus engines detected LJSONedit.exe?
What is the SHA-256 hash of LJSONedit.exe?
Is it safe to run LJSONedit.exe?
How up to date is this analysis of LJSONedit.exe?
Community
Member reviews and reports for this exact file hash.