File scan report
Verdict Suspicious
Is com. 2manyrobots. Yate safe? Treat it as suspicious.
Three major antivirus engines flag a unwanted program label on a self-signed DMG with no established signer history.
Read the whole reasonShow less
Why Suspicious? 6 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat the DMG as untrusted; verify the source and consider an alternative, signed distribution from a known vendor before installation.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumMac malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from a MacClear step-by-step instructions. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
6 of 59 flagged
- Flagged 6
- No detection 53
- No result 16
- Code signing Signer not verified
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
3 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Six of the 59 antivirus engines that checked it flag the file, three of them major, 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 unwanted program detections from major antivirus engines, an unsigned-publisher signer string, and direct-IP traffic without domain names creates mixed signals. This places the file in the suspicious band rather than malicious or safe.
What We Detected
Three less reliable engines (Avast, AVG, Avira) and three additional engines returned unwanted program 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
- 11 major antivirus engines reported it clean and tier1Total=17 — majority of major antivirus 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.
- No malicious sandbox verdict
- No malicious files it created or contacted hosts
- Self-signed by unknown publisher
- Three unwanted program detections from major antivirus engines
- Direct-IP traffic without domain names
6 sources checked · 5 complete · 1 partial. 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- 3sandbox rule tags
- 6spawned processes
- 20network contacts
- 5filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Note: Talked to servers over the internet during the test run.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
com.2manyrobots.Yate
16e105c9ffb60aa98ef689750f3243e2eaa1e31b940ac2e6e1694405f5e79f6d
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
online-auth-agent
/usr/libexec/online-auth-agent
Test run - Evidence 3 of 7: ProcessSeen in the test run
homeenergyd
/System/iOSSupport/System/Library/PrivateFrameworks/HomeEnergyDaemon.framework/Support/homeenergyd
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
data.data
/Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/data.data
Test run - Evidence 5 of 7: Written fileSeen in the test run
windows.plist
/Users/user1/Library/Saved Application State/com.2manyrobots.Yate.savedState/windows.plist
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
96.16.55.163
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
72.21.91.29
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 3 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
6 of the 59 antivirus engines that checked it flag it; a signature that did not verify.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 6
- Avast (major engine)MacOS:TNT-A [PUP]
- AVG (major engine)MacOS:TNT-A [PUP]
- Avira (major engine)PUA/OSX.TNT.A
- F-Secure (major engine)PotentialRisk.PUA/OSX.TNT.A
- GData (major engine)Generic.Trojan.Agent.CJH9NS
- CynetMalicious (score: 99)
File fingerprint
- Last analyzed
- Sep 2, 2026, 12:59 AM UTC
- SHA-256
16e105c9ffb60aa98ef689750f3243e2eaa1e31b940ac2e6e1694405f5e79f6d- SHA-1
92387ade48a11b8feae4ca01934d092d27499297- MD5
43a37abd0e0b246e6aad8e0f48fda1c7
About this file
com.2manyrobots.Yate is a Macintosh Disk Image file of 15.9 MB.
- Type and size
- Macintosh Disk Image · 15.9 MB
- Signer
- TNT - why join the navy if you can be a pirate (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Jul 3, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75) and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 7 questions people ask most about this file.
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?
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.