Unknown
New unsigned ARM ELF with zero engine detections but only one submission so far.
3d18e03f1430303137…d7299ddeeaThe reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
Zero malicious detections across tier-1, tier-2, and low-trust engines combined with no sandbox or network evidence point to a clean file. However, the sample is only hours old, has a single submission, and is unsigned, so coverage is too low to issue a confident safe verdict. The absence of any YARA, CIRCL, or MalwareBazaar signals further supports a neutral stance rather than a malicious classification.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1Malicious=0 and engines.malicious=0 across 63 reporting engines
prevalence.classification=rare_new with firstSubmissionDate 2026-07-09
signing.verified=null (unsigned) and signing.signerStats.found=false
externalIntel.yaraify.ruleCount=0 and externalIntel.malwareBazaar.hit=false
- Zero detections from 17 tier-1 engines
- No external intelligence hits
- Unsigned binary
- rare_new prevalence
- Zero days since first submission
Re-submit after broader distribution or run the binary in a sandbox to gather behavioural data before trusting it.
What to do now
There isn't enough information to give this file a clear rating.
Be cautious — an unknown rating is not the same as a clean bill of health.
Only run it if it came directly from the official maker of the software.
When in doubt, don't open it — or scan it again later once it's more widely seen.
0 detections across 74 engines
How widely this file has been seen
Barely seen in the wild and first surfaced recently. This is the footprint of targeted malware the AV industry hasn't signatured yet — extra scrutiny is warranted.
Forensic fingerprint
- File name
- harbour-sailwarden
- Size
- 1.49 MB
- MIME type
- (unknown)
- Detected type
- ELF
- SHA-256
- 3d18e03f14303031376611744c06417d3987175ebe10555f0df216d7299ddeea
- MD5
- 0b9e658f58a171690ccbe99550c20ca1
- SHA-1
- 8ee5e394d4a8d2d6d698796d40a40f432f974cd3
- First seen (VT)
- 7/9/2026, 4:25:32 AM
- Last analysis (VT)
- 7/9/2026, 4:25:32 AM
- First scan (MalwareTips)
- 7/9/2026, 4:32:48 AM
- Last scan (MalwareTips)
- 7/9/2026, 4:32:48 AM
Safety FAQ
Common questions about harbour-sailwarden, answered from the scan data above.
- We can't give harbour-sailwarden a confident verdict yet — too few engines have an opinion on this exact file. Uncommon or brand-new files often show little coverage before vendors catch up, so treat it as untrusted: don't opened it unless you're certain of the source.
- harbour-sailwarden is a file, about 1.5 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- None — all 74 antivirus engines we queried report harbour-sailwarden as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- The SHA-256 hash of harbour-sailwarden is 3d18e03f14303031376611744c06417d3987175ebe10555f0df216d7299ddeea, and its MD5 is 0b9e658f58a171690ccbe99550c20ca1. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 9, 2026. Because a file's hash never changes, the identity of harbour-sailwarden is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.