File scan report
Verdict Safe
Is tacky-
None of the 67 antivirus engines that checked it flagged this window-border utility archive, and its single sandbox run returned clean with only app-specific config and log files…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This archive appears to be the tacky-borders utility and is reasonable to use if it came from the official project source. Keep your antivirus enabled while running it.
Good practice2 tips
We found nothing harmful in this file.
Open it only if you trust the person or website you got it from.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 67 flagged
- Flagged 0
- No detection 67
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
1 point against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
In a sandbox it extracted and ran tacky-borders.exe, which wrote its own config and log files and installed no persistence. The run mapped a process-injection technique without naming any target, which is common for tools that draw over other windows.
The archive has zero detections across 75 engines, including all reporting major antivirus engines. Activity in the test run was limited to extracting and launching tacky-borders.exe, which created an app-named program markers and wrote config and log files. Missing host-reputation coverage and unverdicted dropped files are neutral gaps rather than risk.
What We Detected
None of the 67 antivirus engines that checked it flagged this ZIP archive. Researcher feeds and YARA rule sets returned no matches. The file has been seen by 18 submitters over 77 days.
Threat Behavior
In one sandbox run, the archive extracted tacky-borders.exe and launched it. The program wrote a config.yaml and a log file under its own .config folder and created an app-named program markers. No persistence, registry changes or network contacts were recorded. The sandbox mapped process-injection and defense-impairment techniques, but no injected target process was identified. Window-border tools commonly interact with other windows in ways that trigger these mappings. A complete host-reputation result and verdicts for the four dropped files are not available.
What To Do Now
Download releases only from the project's official source. Keep your antivirus enabled while running the tool.
Where this verdict could be wrong2 caveats
- The sandbox mapped process injection and defense-impairment techniques. No injected process was named, and border-drawing tools commonly hook other windows, which can produce such mappings.
- Only one sandbox run exists, and the four dropped files have no saved verdict.
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 67 antivirus engines that checked it flagged the file
- The single sandbox run returned clean
- Activity in the test run was limited to the app's own config and log files, with no persistence
- No hits in malware sample feeds or YARA rule sets
- The sandbox mapped process-injection and defense-impairment techniques, though no target process was identified
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 our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 7sandbox rule tags
- 5spawned processes
- 0network contacts
- 12filesystem & mutex artifacts
Includes the sandbox verdicts, 7 mapped techniques, every process, file, registry and network entry and 4 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 67 antivirus engines that checked it flag it.
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 17, 2026, 7:47 PM UTC
- SHA-256
eb75ad4b6b22935f6ceb2e12e36c55bcdf907176953eb47ec7038e4b60a48f23- SHA-1
970b72332be9c7f45ced3f882d4d13dd30b34999- MD5
dba8ca73284d39da636e7997a07dd038
About this file
tacky-borders-v1.6.0.zip is a ZIP file of 1.3 MB.
- Type and size
- ZIP · 1.3 MB
- Signer
- Not applicable
- First seen
- Aug 2, 2026On VirusTotal.
- Submitted by
- 18 distinct sources
First scanned
Includes every engine result (75), 1 matched signature rule 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 tacky-borders-v1.6.0.zip safe?
What is tacky-borders-v1.6.0.zip?
How many antivirus engines detected tacky-borders-v1.6.0.zip?
What is the SHA-256 hash of tacky-borders-v1.6.0.zip?
Is it safe to open or extract tacky-borders-v1.6.0.zip?
How up to date is this analysis of tacky-borders-v1.6.0.zip?
Community
Member reviews and reports for this exact file hash.