Is sqldiff safe?
No engine detected malware, and one sandbox found no offensive behavior, dropped payloads, persistence, or malicious runtime verdict despite limited network-reputation coverage.
None of 74 antivirus engines flagged this Mach-O, including the reporting tier-1 products. One sandbox observed only ambient techniques and produced no malicious verdict, although the unsigned file's direct-IP traffic was not fully covered by host-reputation checks.
aaf684cf784ea1d380…dd8be38a9e4f83Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
None of 74 antivirus engines flagged this Mach-O, including the reporting tier-1 products. One sandbox observed only ambient techniques and produced no malicious verdict, although the unsigned file's direct-IP traffic was not fully covered by host-reputation checks.
The strongest evidence is the complete absence of detections across 74 antivirus engines, with 16 tier-1 products reporting no detection. A completed sandbox run recorded no offensive techniques, persistence indicators, dropped payloads, or malicious verdict. The direct-IP heuristic is a legitimate caution, but the recorded URLs are certificate-status requests and no independent source corroborated command-and-control activity. Only two contacted hosts were reputation-checked despite many observed IPs and URLs, so the no complete contacted-host reputation result was available. The missing signature reduces publisher assurance but does not outweigh the broad engine results and uneventful runtime observation.
What We Detected
None of 74 antivirus engines flagged the Mach-O, and 16 tier-1 engines reported no detection. Research feeds also returned no MalwareBazaar, CIRCL, or YARAify match.
Threat Behavior
One sandbox run recorded two ambient techniques but no offensive techniques, persistence indicators, dropped payloads, or malicious sandbox verdict. A medium-severity direct-IP heuristic fired, although the recorded URLs were OCSP certificate-status requests and several addresses appear associated with common DNS or CDN infrastructure. Only two hosts were checked against the reputation cache, so complete reputation coverage of all observed contacts is unavailable.
What To Do Now
Obtain the file from the official SQLite or trusted package channel and verify its SHA-256 before execution. Keep endpoint protection enabled, particularly because the binary is unsigned and its publisher identity cannot be verified.
Where this verdict could be wrong2 caveats
- MalwareTips.Synth.DirectIpC2 fired after direct connections to numerous IP addresses without application-domain attribution; contactedHosts.inspected=2 does not cover all observed contacts.
- signing.signed=false means the Mach-O has no verified publisher identity.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 engines reported a malicious or suspicious result.
- tier1Malicious=0, while 16 tier-1 engines reported no detection.
- behaviour.offensiveCount=0 and behaviour.hasMaliciousSandboxVerdict=false.
- No persistence indicators or dropped-file hashes were observed.
- YARAify, CIRCL, and MalwareBazaar returned no hits.
- The Mach-O is unsigned, so no publisher identity is available.
- MalwareTips.Synth.DirectIpC2 fired for numerous direct-IP contacts.
- contactedHosts.inspected=2 provides only partial reputation coverage of the observed network contacts.
- prevalence.uniqueSources=1 and prevalence.timesSubmitted=1 provide limited submission history.
Use the binary only if its SHA-256 matches an official or trusted distribution of sqldiff. Keep endpoint protection enabled and avoid the file if its source cannot be verified.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 22 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 2MITRE ATT&CK techniques
- 7spawned processes
- 26network contacts
- 2filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
sqldiff
aaf684cf784ea1d380042857b46e3122707b95c35b60b0b004dd8be38a9e4f83
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
/bin/zsh
02Isolated runtime analysis - ProcessObserved
Observed process
/usr/bin/env
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
.dat.nosync0200.GCqZy0
/Users/user1/Library/Application Support/com.apple.spotlight/.dat.nosync0200.GCqZy0
04Isolated runtime analysis - Written fileObserved
UserTrust.db-shm
/private/var/db/MobileIdentityService/Configuration/UserTrust.db-shm
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
8.8.8.8
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
72.21.91.29
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 8.8.8.8
- 72.21.91.29
- 104.18.38.233
- 255.255.255.255
- 23.220.75.235
- 172.64.149.23
- 23.56.109.238
- 23.56.109.230
- 162.159.142.9
- 23.11.32.159
- http://ocsp.usertrust.com/MFYwVKADAgEAME0wSzBJMAkGBSsOAwIaBQAEFM0w0kw0OoKrHwVwFYrXoQd2KZLpBBRTeb9aqitKz1SA4dibwJ3ysgNmywIQXfq7lXfPq2cfx93%2B0c8gWw%3D%3D
- http://ocsp.comodoca.com/MFcwVaADAgEAME4wTDBKMAkGBSsOAwIaBQAEFOsl2JD%2BJyD0HX1qwV7vds9iz6t4BBR1cacZSBm8nZ3qQUfflMRId5nTeQIRAJjBcnaqg2kI3NxbTvi9QXQ%3D
- http://ocsp.comodoca.com/MFcwVaADAgEAME4wTDBKMAkGBSsOAwIaBQAEFOsl2JD+JyD0HX1qwV7vds9iz6t4BBR1cacZSBm8nZ3qQUfflMRId5nTeQIRAJjBcnaqg2kI3NxbTvi9QXQ=
- http://ocsp.usertrust.com/MFYwVKADAgEAME0wSzBJMAkGBSsOAwIaBQAEFM0w0kw0OoKrHwVwFYrXoQd2KZLpBBRTeb9aqitKz1SA4dibwJ3ysgNmywIQXfq7lXfPq2cfx93+0c8gWw==
- http://ocsp.comodoca.com/MFAwTjBMMEowSDAHBgUrDgMCGgQU6yXYkP4nIPQdfWrBXu92z2LPq3gEFHVxpxlIGbydnepBR9+UxEh3mdN5AhEAmMFydqqDaQjc3FtO+L1BdA==
- http://ocsp.usertrust.com/ME8wTTBLMEkwRzAHBgUrDgMCGgQUzTDSTDQ6gqsfBXAVitehB3YpkukEFFN5v1qqK0rPVIDh2JvAnfKyA2bLAhBd+ruVd8+rZx/H3f7RzyBb
- /Users/user1/Library/Application Support/com.apple.spotlight/.dat.nosync0200.GCqZy0
- /private/var/db/MobileIdentityService/Configuration/UserTrust.db-shm
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 74engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: sqldiff — aaf684cf784ea1d380042857b46e3122707b95c35b60b0b004dd8be38a9e4f83
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — /bin/zsh
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /usr/bin/env
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: .dat.nosync0200.GCqZy0 — /Users/user1/Library/Application Support/com.apple.spotlight/.dat.nosync0200.GCqZy0
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: UserTrust.db-shm — /private/var/db/MobileIdentityService/Configuration/UserTrust.db-shm
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 8.8.8.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 72.21.91.29 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence72.21.91.29 · 104.18.38.233 · 23.220.75.235
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- sqldiff
- Format
- Mach-O
- Code signing
- No verified publisher
- Size
- 1.6 MB
- Last analyzed
- Sep 22, 2026, 2:44 AM UTC
aaf684cf784ea1d380042857b46e3122707b95c35b60b0b004dd8be38a9e4f83Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is sqldiff safe?
What is sqldiff?
How many antivirus engines detected sqldiff?
What is the SHA-256 hash of sqldiff?
Is it safe to run sqldiff?
How up to date is this analysis of sqldiff?
Community
Member reviews and reports for this exact file hash.