Is com.apphousekitchen.aldente-pro safe?
No antivirus engine identified a threat, and the completed sandbox run found no offensive behavior, though direct-IP traffic remains incompletely reputation-checked.
All 75 antivirus engines produced no malicious or suspicious detection, including 17 tier-1 engines. One sandbox run found no offensive techniques, persistence, malicious verdict, or confirmed malicious child, but the observed direct-IP endpoints were not fully reputation-checked and the signer lacks verification history.
2457dc71bc462f462a…9d3c1f9a49d8bfRecommended next actions
Before opening
Open it only when its sender or download source is one you independently trust.
If you already opened 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.
All 75 antivirus engines produced no malicious or suspicious detection, including 17 tier-1 engines. One sandbox run found no offensive techniques, persistence, malicious verdict, or confirmed malicious child, but the observed direct-IP endpoints were not fully reputation-checked and the signer lacks verification history.
The disk image received no malicious or suspicious detections from 75 engines, with all 17 tier-1 engines silent. A completed sandbox run recorded only ambient techniques and produced no malicious sandbox verdict, offensive behavior, or persistence indicators. Ten dropped children were inspected without a confirmed malicious result, although their individual verdicts remain unknown. The main counter-signal is direct-IP network activity identified by MalwareTips.Synth.DirectIpC2. Because no complete host-reputation result is available and the signer has no verified history, some residual uncertainty remains despite the otherwise reassuring evidence.
What We Detected
None of 75 antivirus engines flagged the disk image, and all 17 tier-1 engines reported no detection. Research feeds also returned no MalwareBazaar, CIRCL, or YARAify match.
Threat Behavior
One completed sandbox run showed no offensive techniques, persistence indicators, or malicious sandbox verdict. Ten dropped children were inspected without a confirmed malicious child, but their individual verdicts remain unknown. The run contacted several IP addresses directly, triggering MalwareTips.Synth.DirectIpC2; because contactedHosts is unavailable, no complete reputation result exists for those endpoints.
What To Do Now
Obtain the disk image from the application's official release channel and verify its macOS signature or notarization before installation. Keep endpoint protection enabled and avoid granting unnecessary permissions if macOS presents publisher or trust warnings.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.DirectIpC2 fired after direct connections to multiple IP addresses without recorded application domains; contactedHosts=null leaves their reputation unresolved.
- The image is signed by 'TEAM EDiSO', but signing.verified=null and signing.signerStats.found=false provide no verified or historical publisher trust.
- All 10 inspected dropped children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false does not establish that each child is benign.
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/75 engines reported malicious or suspicious findings.
- All 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false with behaviour.offensiveCount=0.
- No persistence indicators were observed.
- No external-intelligence or YARAify match was found.
- Direct-IP network activity triggered MalwareTips.Synth.DirectIpC2.
- contactedHosts=null, so endpoint reputation coverage is incomplete.
- signing.verified=null for signer 'TEAM EDiSO'.
- signing.signerStats.found=false, leaving no established signer history.
- All 10 dropped-child verdicts are individually unknown.
Use only a copy obtained from the application's official source, and verify macOS signature or notarization before opening it. Keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
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
- 13spawned processes
- 20network contacts
- 30filesystem & 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
com.apphousekitchen.aldente-pro
2457dc71bc462f462a21edd77bdbe7810f8020c1e5cb0692199d3c1f9a49d8bf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
/bin/ps
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
en_US.cshelpindex
/Users/admin/Library/Caches/com.apple.helpd/Generated/final-cut-pro/en_US.cshelpindex
04Isolated runtime analysis - Written fileObserved
PCSAnalytics.db-shm
/Users/admin/Library/Application Support/com.apple.ProtectedCloudStorage/PCSAnalytics.db-shm
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
151.101.3.6
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.11.32.159
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.
- 151.101.3.6
- 23.11.32.159
- 23.218.145.106
- 23.222.245.13
- 23.11.40.157
- 17.57.146.7
- 17.253.29.149
- 185.196.12.16
- 17.250.81.68
- 17.253.29.134
- /Users/admin/Library/Caches/com.apple.helpd/Generated/final-cut-pro/en_US.cshelpindex
- /Users/admin/Library/Application Support/com.apple.ProtectedCloudStorage/PCSAnalytics.db-shm
- /Users/admin/Library/Caches/com.apple.helpd/fsCachedData/1AB3B9DB-5698-4C2B-AB77-B36F773EFCD5.tmp
- /Users/admin/Library/Caches/com.apple.helpd/fsCachedData/677B3126-8590-4876-A4EE-7126B6E2224A.tmp
- /Users/admin/Library/Caches/com.apple.helpd/Generated/com.apple.fontbook.help*11.0/en_US.cshelpindex
- /Users/admin/Library/Caches/com.apple.helpd/fsCachedData/A06463AD-20E9-4AD8-A312-67B14B1DB000
- /Users/admin/Library/Containers/com.apple.BKAgentService/Data/tmp/TemporaryItems/NSIRD_com.apple.BKAgentService_G5yjd2
- /Users/admin/Library/Caches/com.apple.helpd/fsCachedData/21083FC3-5CE1-4063-BDEA-2578BA4A5185
- /private/var/db/powerlog/Library/BatteryLife/Archives/powerlog_2026-04-05_1959A502.PLSQL-shm
- /Users/admin/Library/Caches/com.apple.helpd/fsCachedData/24B35FAE-3862-4EAF-B70F-E51EEA5CCCF0
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 33b009a19831bb478ae9…4e0a58Never scannednever seen before
- 0ef2b90793cebe28145b…f54815Never scannednever seen before
- 302fe54c85073a03f2ae…ed5442Never scannednever seen before
- e3b0c44298fc1c149afb…52b855Never scannednever seen before
- d000482dc99e58a08f21…0adfd2Never scannednever seen before
- 14aeb7ef00d57f89469d…5f15d5Never scannednever seen before
- 1e14cc14ce38acbea277…83d3a8Never scannednever seen before
- 24b8218ae4d81c0c28c2…c2b3e9Never scannednever seen before
- de198e00c4ccb669fae5…2aff07Never scannednever seen before
- 75f2c635671e3199e345…a274c3Never scannednever seen before
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 / 75engines flagged
- 10sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 10 times from 10 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: com.apphousekitchen.aldente-pro — 2457dc71bc462f462a21edd77bdbe7810f8020c1e5cb0692199d3c1f9a49d8bf
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — /bin/ps
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /usr/bin/env
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: en_US.cshelpindex — /Users/admin/Library/Caches/com.apple.helpd/Generated/final-cut-pro/en_US.cshelpindex
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: PCSAnalytics.db-shm — /Users/admin/Library/Application Support/com.apple.ProtectedCloudStorage/PCSAnalytics.db-shm
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 151.101.3.6 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 23.11.32.159 — 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.
Evidence151.101.3.6 · 23.11.32.159 · 23.218.145.106
0 of 75 engines flagged this file
View all 75 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
- com.apphousekitchen.aldente-pro
- Format
- Macintosh Disk Image
- Code signing
- Signature not verified: TEAM EDiSO
- Size
- 12.0 MB
- Last analyzed
- Sep 15, 2026, 4:42 PM UTC
2457dc71bc462f462a21edd77bdbe7810f8020c1e5cb0692199d3c1f9a49d8bfSafety & 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
Open it only when its sender or download source is one 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 com.apphousekitchen.aldente-pro safe?
What is com.apphousekitchen.aldente-pro?
How many antivirus engines detected com.apphousekitchen.aldente-pro?
Is com.apphousekitchen.aldente-pro digitally signed?
What is the SHA-256 hash of com.apphousekitchen.aldente-pro?
Is it safe to open com.apphousekitchen.aldente-pro?
How up to date is this analysis of com.apphousekitchen.aldente-pro?
Community
Member reviews and reports for this exact file hash.