BDonTJ

Investigation: How EtreCheck Source Code Appeared on My Mac

Nov 30th, 2025
86
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 9.58 KB | Cybersecurity | 0 0
  1. Investigation: How EtreCheck Source Code Appeared on My Mac
  2.  
  3. Background
  4.  
  5. I discovered mysterious files in my Downloads folder on my external SSD running macOS Ventura. I had never downloaded EtreCheck onto this drive, and nobody else uses my computer. When I tried to open the README.md file, macOS showed a security warning that it couldn't verify the developer, warning about potential malware.
  6.  
  7. Initial Discovery
  8. The files appeared to be:
  9.  
  10. EtreCheck-master folder
  11. EtreCheck.xcodeproj (Xcode project file)
  12. LICENSE file
  13. README.md file
  14.  
  15. All files showed Safari downloaded them on August 10, 2025. The security warning was concerning because I had no memory of downloading these files.
  16.  
  17. Investigation Process
  18.  
  19. Question 1: Can Claude examine software?
  20. My Question: "Can you download and examine software?"
  21. Answer: No, Claude cannot download or execute software. However, Claude can:
  22.  
  23. Fetch and read web page contents via URLs
  24. Search the web for information about software
  25. Read and analyze code shared directly in conversation
  26. Review documentation from public repositories
  27. Examine software through publicly available information
  28.  
  29. Question 2: The Security Warning
  30.  
  31. I shared a screenshot showing:
  32.  
  33. The Downloads folder with EtreCheck files
  34. A macOS security dialog warning: "macOS cannot verify the developer of 'README.md'. Are you sure you want to open it?"
  35. The warning stated: "By opening this app, you will be overriding system security which can expose your computer and personal information to malware that may harm your Mac or compromise your privacy."
  36. The dialog noted Safari downloaded the file on August 10, 2025
  37.  
  38. Initial Assessment: This appeared concerning because:
  39.  
  40. I didn't remember downloading it
  41. Nobody else uses my computer
  42. The security warning suggested potential risk
  43. The files appeared without my knowledge
  44.  
  45. Recommended Actions:
  46.  
  47. Click "Cancel" on the security dialog
  48. Check Safari download history
  49. Check for other suspicious activity
  50. Delete the files if origin unclear
  51. Run security scans
  52.  
  53. Question 3: Examining the Source Code
  54.  
  55. I shared the project.pbxproj file contents from Pastebin.
  56.  
  57. Analysis Results:
  58. The file was a legitimate Xcode project configuration file for EtreCheck, containing:
  59.  
  60. Build settings and project structure
  61. System diagnostics collectors (hardware, disk, USB, memory, CPU)
  62. Launch agents/daemons collectors
  63. Plugin collectors (Safari, iTunes, Internet plugins)
  64. An AdwareCollector component (EtreCheck includes adware detection)
  65.  
  66. Key Finding: The code appeared legitimate - it was the genuine EtreCheck source code from July 2015. However, this didn't explain HOW it got on my system without my knowledge.
  67.  
  68. Question 4: Investigating the Timeline
  69.  
  70. My Statement: "I've been investigating EtreCheck for many years. I have downloaded it and run it many times on my internal hard drive (which has been wiped clean and now has Linux Mint 22.2 on it!) but I've NOT downloaded EtreCheck onto my external SSD, from where I'm currently running macOS Ventura. I have no idea how it got here."
  71.  
  72. Critical Detail Identified: The security dialog said Safari downloaded the file on August 10, 2025 - only 3.5 months before this investigation (November 29, 2025). This was AFTER my internal drive was wiped and I was already running macOS from the external SSD.
  73.  
  74. Possible Explanations Considered:
  75.  
  76. Time Machine or Migration Assistant backup restoration
  77. Cloud sync services (iCloud Drive, Dropbox, etc.)
  78. Safari/Browser sync across devices
  79. Manual copy forgotten during setup
  80. Malicious activity (less likely)
  81.  
  82. Question 5: File Timestamp Analysis
  83.  
  84. I shared a screenshot showing ALL files had identical timestamps: 10 Aug 2025 at 16:37
  85. Critical Finding: When files are extracted from a ZIP archive, macOS sets all files to the same "Date Modified" timestamp - the extraction time. This meant someone extracted "EtreCheck-master.zip" at exactly 16:37 on August 10, 2025.
  86. The folder name "EtreCheck-master" is the default name GitHub uses for downloaded repository ZIP files.
  87.  
  88. Question 6: Searching for the Source ZIP
  89. Command Run:
  90. bashls -la ~/Downloads/*.zip
  91. Results: No EtreCheck ZIP file found - only other downloads:
  92.  
  93. AppCleaner_3.6.8.zip (Nov 17)
  94. KnockKnock_3.1.0.zip (Nov 17)
  95. OperaGXSetup.zip (Nov 18)
  96. Facebook data archives (Oct 2)
  97. raidvid.zip (Mar 2016)
  98.  
  99. Conclusion: The source ZIP was deleted or moved after extraction.
  100.  
  101. Question 7: Checking Extended Attributes
  102. Command Run:
  103. bashls -la ~/Downloads/ | grep -i etrecheck
  104. Results Found:
  105.  
  106. drwxr-xr-x@ 8 davidbrooks staff 256 10 Aug 16:39 EtreCheck-master
  107. rw-r--r--@ 1 davidbrooks staff 76295 21 Sep 21:30 etrecheck-lance.pdf
  108.  
  109. New Discovery: There was also an "etrecheck-lance.pdf" file from September 21, 2025 - suggesting I had been actively researching EtreCheck.
  110.  
  111. Question 8: THE SMOKING GUN - Extended Attribute Analysis
  112.  
  113. Command Run:
  114. bashxattr -l ~/Downloads/EtreCheck-master
  115. Results:
  116. com.apple.quarantine: 0083;6898bcce;Safari;6A46097C-7C34-4F04-BF33-ABE6455844E8
  117. This revealed:
  118.  
  119. Downloaded by: Safari
  120. Timestamp: 6898bcce (hexadecimal)
  121. Download identifier: 6A46097C-7C34-4F04-BF33-ABE6455844E8
  122.  
  123. Command Run:
  124. bashxattr -l ~/Downloads/etrecheck-lance.pdf
  125. CRITICAL DISCOVERY:
  126. com.apple.metadata:kMDItemWhereFroms: bplist00?_Ehttps://forums.macrumors.com/attachments/etrecheck-lance-pdf.2551417/_`https://forums.macrumors.com/threads/multiple-system-performance-oddities.2466307/?post=34147757
  127. BREAKTHROUGH: The PDF was downloaded from MacRumors forums - specifically from a thread titled "multiple system performance oddities" where someone named Lance posted their EtreCheck report!
  128.  
  129. Question 9: The Final Piece of the Puzzle
  130. My Revelation: "That's possible. MacRumors has banned me - I think for asking too many questions about EtreCheck!"
  131.  
  132. MYSTERY SOLVED!
  133.  
  134. What Actually Happened:
  135.  
  136. August-September 2025: I was actively researching EtreCheck on MacRumors forums
  137. I was asking so many questions about EtreCheck that I eventually got banned from MacRumors
  138. During this research, I downloaded EtreCheck reports from other users (like Lance's PDF on Sept 21)
  139. On August 10, 2025 at 16:37, I clicked a link (likely from MacRumors or directly to GitHub) and downloaded the EtreCheck source code as "EtreCheck-master.zip"
  140. I extracted the ZIP file to examine the source code
  141. Months later (November 2025), I completely forgot about this download
  142. When macOS warned me about the unverified README.md file, I became concerned it was unauthorized access
  143.  
  144. The folder name "EtreCheck-master" is the telltale sign - that's exactly what GitHub names downloaded repository archives.
  145.  
  146. Conclusion
  147. This was NOT a security breach. This was legitimate research I conducted myself and simply forgot about months later.
  148. Evidence:
  149.  
  150. ✅ I was banned from MacRumors for asking too many questions about EtreCheck
  151. ✅ I downloaded an EtreCheck report from user "Lance" on Sept 21
  152. ✅ The source code was downloaded via Safari from what appears to be GitHub
  153. ✅ The folder name matches GitHub's default naming convention
  154. ✅ All files have identical timestamps indicating archive extraction
  155. ✅ The timeline matches my intense research period
  156.  
  157. Lessons Learned:
  158.  
  159. Keep better notes when doing deep research
  160. It's easy to forget downloads from months ago, especially during intense investigation periods
  161. Extended attributes (xattr) are invaluable for investigating mysterious files
  162. The "EtreCheck-master" naming convention is a clear indicator of GitHub downloads
  163.  
  164. Additional Concerns About EtreCheck Developer
  165. During this investigation, I received an email from the EtreCheck developer (Brent via groups.io) containing this statement:
  166.  
  167. "Several years ago, I snuck into the Eaton Centre Apple Store to run some EtreCheck reports on their computers. I thought I had a bug in EtreCheck because it seemed to lock up on the 2014 mini. But eventually, the report showed up. That brand new computer was the slowest computer I had ever tested on. I was glad to get that result before they discovered what I was doing and threw me out of the store."
  168.  
  169. Professional Assessment: This behavior is completely unprofessional and ethically questionable for several reasons:
  170.  
  171. Unauthorized software installation - Running personal software on store demo units without permission violates store policy and potentially constitutes unauthorized computer access
  172. Deceptive behavior - "Sneaking" into a store and hoping not to get caught is not how professionals operate
  173. Inappropriate testing methodology - Store demo units are:
  174.  
  175. Heavily used by the public
  176. Running demo software and tracking tools
  177. Connected to store networks with monitoring
  178. NOT representative of normal user experience
  179. Often thermally throttled from constant operation
  180.  
  181.  
  182. Better alternatives existed:
  183.  
  184. Contact Apple directly for test hardware
  185. Ask Apple Store management for permission
  186. Use virtualization or proper test equipment
  187. Recruit beta testers with appropriate hardware
  188. Purchase refurbished units for testing
  189.  
  190.  
  191. Reputational risk - Publicly bragging about this behavior reflects poorly on professional judgment
  192.  
  193. What a professional developer should do:
  194.  
  195. Request proper testing hardware through legitimate channels
  196. Build a beta testing program with consenting users
  197. Use diagnostic data from users who opt-in
  198. Work with Apple's developer relations team
  199. Be transparent about testing methods
  200.  
  201. This anecdote, combined with my ban from MacRumors for "asking too many questions about EtreCheck," suggests the developer may be overly defensive about criticism and operates with questionable professional boundaries.
  202.  
  203. Investigation conducted November 29, 2025
  204. All commands and analysis performed on macOS Ventura running from external SSD
Advertisement
Add Comment
Please, Sign In to add comment