File scan report
Verdict Suspicious
Is harver- system- checker. exe safe? Treat it as suspicious.
The file is signed by Harver B.V. but lacks established reputation.
Why Suspicious? One antivirus engine (Dr.Web) flags it; nothing else confirms it.
Limited evidence
Treat as suspicious. Verify the source of the file and monitor its behaviour in a restricted environment.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 66 flagged
- Flagged 1
- No detection 65
- No result 7
- Code signing Harver B.V.
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Our analysis shows a signed file with rare prevalence and complex behavioural patterns. The mixed signals from similar hashes further support a cautious classification. We recommend treating this file as suspicious until further evidence of malicious intent is observed.
What We Detected
The file harver-system-checker.exe is a signed Win32 executable. While it carries a valid signature from 'Harver B.V.', it lacks a track record in our database. Only 1 of the 66 antivirus engines that checked it flagged the file, specifically identifying it as Trojan.Siggen15.22474.
Threat Behavior
These patterns often trigger rule-based alerts. However, these techniques are also common in complex, legitimate software installers that perform system diagnostics or updates. No complete contacted-host reputation result was available.
What To Do Now
Given the mixed signals, we advise caution. If this file was obtained from an official source related to Harver B.V., it may be legitimate. If the source is unknown or untrusted, we recommend restricting its execution in a sandboxed environment or monitoring its network activity closely.
Where this verdict could be wrong2 caveats
- The file is signed by a valid corporate entity, which often accounts for complex installation behaviours that trigger rule-based alerts.
- The lack of malicious hits in our URL/IP cache and the absence of malicious files it created suggest the file may be benign despite its complex behaviour.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Valid code signature from 'Harver B.V.'
- Only 1/66 engines flagged as malicious
- No malicious files it created
- Rare prevalence (2 submissions)
- Direct-IP communication detected
- No established signer history
6 sources checked · 5 complete · 1 partial. 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- 24sandbox rule tags
- 4spawned processes
- 4network contacts
- 33filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
harver-system-checker.exe
4ffc6e789f9f35d313ef3ed75b44bab98240da082a0f700a3ab99d951b931df3
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
4ffc6e789f9f35d313ef3ed75b44bab98240da082a0f700a3ab99d951b931df3.exe
Test run - Evidence 3 of 7: ProcessSeen in the test run
Harver System Checker.exe
%USERPROFILE%\AppData\Local\Programs\@harversaas-diagnostic-app\Harver System Checker.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsk86CB.tmp\System.dll
Test run - Evidence 5 of 7: Written fileSeen in the test run
StdUtils.dll
C:\Users\<USER>\AppData\Local\Temp\nsk86CB.tmp\StdUtils.dll
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
172.217.13.238
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
216.239.32.29
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 24 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 66 antivirus engines that checked it flags it; signed by Harver B.V..
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- DrWeb (major engine)Trojan.Siggen15.22474
File fingerprint
- Last analyzed
- Jul 23, 2026, 8:58 PM UTC
- SHA-256
4ffc6e789f9f35d313ef3ed75b44bab98240da082a0f700a3ab99d951b931df3- SHA-1
f882ad078390a7c19bf3a84ccef76729d146a0ee- MD5
506f3f725b514151736d25cf10610fce
About this file
harver-system-checker.exe is a Win32 EXE file of 53.5 MB.
- Type and size
- Win32 EXE · 53.5 MB
- Signer
- Harver B.V.Valid code signature.
- First seen
- Oct 13, 2021On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Includes every engine result (73), 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 7 questions people ask most about this file.
Is harver-system-checker.exe safe, or is it malware?
What is harver-system-checker.exe?
How many antivirus engines detected harver-system-checker.exe?
What should I do if I already ran harver-system-checker.exe?
Is harver-system-checker.exe digitally signed?
What is the SHA-256 hash of harver-system-checker.exe?
How up to date is this analysis of harver-system-checker.exe?
Community
Member reviews and reports for this exact file hash.