Is com.2manyrobots.Yate safe?
Three tier-1 engines flag a PUA label on a self-signed DMG with no established signer history.
Six of 75 engines flag the file, three of them tier-1, all pointing to a PUA/OSX.TNT.A family. The DMG is self-signed by an unknown entity and shows direct-IP traffic, yet no malicious sandbox verdict or known-bad hosts were recorded.
16e105c9ffb60aa98e…694405f5e79f6dRecommended next actions
Before opening
Do not open it until the source can be verified independently.
If you already opened it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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.
Six of 75 engines flag the file, three of them tier-1, all pointing to a PUA/OSX.TNT.A family. The DMG is self-signed by an unknown entity and shows direct-IP traffic, yet no malicious sandbox verdict or known-bad hosts were recorded.
The combination of three tier-1 PUA detections, an unsigned-publisher signer string, and direct-IP traffic without domain names creates mixed signals. However, eleven tier-1 engines reported clean, the sandbox produced no malicious verdict, and no dropped child or contacted host carried a prior malicious label. This places the file in the suspicious band rather than malicious or safe.
What We Detected
Three tier-3 engines (Avast, AVG, Avira) and three additional engines returned PUA or generic-trojan labels. The DMG is signed by an entity with no prior sample history in our database.
Threat Behavior
One sandbox run observed direct-IP connections to 18 addresses and no application domains. No MITRE techniques flagged as offensive, and the contacted-host cache returned zero malicious matches.
What To Do Now
Do not run the disk image on production systems. If the file is required, execute it only in an isolated virtual machine and monitor for unexpected outbound traffic.
Where this verdict could be wrong1 caveat
- engines.tier1ReportedClean=11 and tier1Total=17 — majority of tier-1 engines did not flag the file.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 11 tier-1 engines reported clean
- No malicious sandbox verdict
- No malicious dropped children or contacted hosts
- Self-signed by unknown publisher
- Three tier-1 PUA detections
- Direct-IP traffic without domain names
Treat the DMG as untrusted; verify the source and consider an alternative, signed distribution from a known vendor before installation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete6 of 75 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
- 3MITRE ATT&CK techniques
- 6spawned processes
- 24network contacts
- 5filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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.2manyrobots.Yate
16e105c9ffb60aa98ef689750f3243e2eaa1e31b940ac2e6e1694405f5e79f6d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
/usr/libexec/online-auth-agent
02Isolated runtime analysis - ProcessObserved
Observed process
/System/iOSSupport/System/Library/PrivateFrameworks/HomeEnergyDaemon.framework/Support/homeenergyd
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
data.data
/Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/data.data
04Isolated runtime analysis - Written fileObserved
windows.plist
/Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/windows.plist
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
255.255.255.255
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
8.8.8.8
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.
- 255.255.255.255
- 8.8.8.8
- 96.16.55.163
- 72.21.91.29
- 172.64.149.23
- 23.62.54.44
- 67.195.228.56
- 17.253.26.105
- 17.253.27.150
- 23.11.32.159
- http://ocsp.usertrust.com/MFYwVKADAgEAME0wSzBJMAkGBSsOAwIaBQAEFM0w0kw0OoKrHwVwFYrXoQd2KZLpBBRTeb9aqitKz1SA4dibwJ3ysgNmywIQXfq7lXfPq2cfx93%2B0c8gWw%3D%3D
- http://ocsp.comodoca.com/MFcwVaADAgEAME4wTDBKMAkGBSsOAwIaBQAEFOsl2JD%2BJyD0HX1qwV7vds9iz6t4BBR1cacZSBm8nZ3qQUfflMRId5nTeQIRAJjBcnaqg2kI3NxbTvi9QXQ%3D
- http://ocsp.usertrust.com/MFYwVKADAgEAME0wSzBJMAkGBSsOAwIaBQAEFM0w0kw0OoKrHwVwFYrXoQd2KZLpBBRTeb9aqitKz1SA4dibwJ3ysgNmywIQXfq7lXfPq2cfx93+0c8gWw==
- http://ocsp.comodoca.com/MFcwVaADAgEAME4wTDBKMAkGBSsOAwIaBQAEFOsl2JD+JyD0HX1qwV7vds9iz6t4BBR1cacZSBm8nZ3qQUfflMRId5nTeQIRAJjBcnaqg2kI3NxbTvi9QXQ=
- /Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/data.data
- /Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/windows.plist
- /Users/user1/Library/Application Support/com.apple.spotlight/.dat.nosync0200.Sg5eqU
- /Users/bruno/Library/homeenergyd/com.apple.homeenergyd/LocalCache.store-shm
- /private/var/db/MobileIdentityService/Configuration/UserTrust.db-shm
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 88f68531f38551bfbac2…29791bNever scannednever seen before
- 2d78d1583da6c27a3c4e…603b62Never scannednever seen before
- 20d2a699cf22023f1a4c…76b74fNever scannednever seen before
- ad4c7765cd9aa5476286…4c1853Never scannednever seen before
- 44d348da564044c0a3b8…251966Never scannednever seen before
- 82d93f89395280ec116a…197709Never scannednever seen before
- a661c24f6c0fe8b34965…4f51c2Never scannednever seen before
- 0751a8d86e848b7d8086…8de928Never scannednever seen before
- 8772e2486be4b5bd2c69…4e1a5cNever scannednever seen before
- 0c420bfd4be1f509165d…ec3b67Never 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
- 6 / 75engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 of 75 antivirus engines flagged the file, including Avast and AVG.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: com.2manyrobots.Yate — 16e105c9ffb60aa98ef689750f3243e2eaa1e31b940ac2e6e1694405f5e79f6d
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — /usr/libexec/online-auth-agent
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — /System/iOSSupport/System/Library/PrivateFrameworks/HomeEnergyDaemon.framework/Support/homeenergyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: data.data — /Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/data.data
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: windows.plist — /Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/windows.plist
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 255.255.255.255 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 8.8.8.8 — 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.
Evidence96.16.55.163 · 72.21.91.29 · 172.64.149.23
6 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.2manyrobots.Yate
- Format
- Macintosh Disk Image
- Code signing
- Signature not verified: TNT - why join the navy if you can be a pirate
- Size
- 15.2 MB
- Last analyzed
- Sep 2, 2026, 12:59 AM UTC
16e105c9ffb60aa98ef689750f3243e2eaa1e31b940ac2e6e1694405f5e79f6dSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is com.2manyrobots.Yate safe, or is it malware?
What is com.2manyrobots.Yate?
How many antivirus engines detected com.2manyrobots.Yate?
I already downloaded and opened com.2manyrobots.Yate — what should I do?
How do I remove com.2manyrobots.Yate?
Is com.2manyrobots.Yate digitally signed?
What is the SHA-256 hash of com.2manyrobots.Yate?
How up to date is this analysis of com.2manyrobots.Yate?
Community
Member reviews and reports for this exact file hash.