Forks when naming their projects, they shouldn't put misleading names such as OCLP-T2, OpenCоrе-Legacy-Patcher-T2 (with cyrillic o and e) or OpenCore-Legacy-Patcher-2-2. This is an example of typosquatting:
This is considered typosquatting. If typosquatted, one of the following actions may take place:
- Scan the fork for malware (e.g looking for malware in the source code, test it inside a virtual machine or sandbox) by the developer of the main project (Albert Müller)
- If none is found, the developer of the main project (Albert Müller) may open up an issue requesting to rename the project
- If the project is confirmed malicious, the main developer (Albert Müller) may report directly to GitHub
This applies only to forks uploading their forks as projects instead of clicking the Fork button. When clicking the Fork button, by default the name is OpenCore Legacy Patcher T2 and these are less visible in the internet and harder for attackers even to pull off the attack.
Ensure you are running one of the latest up-to-date versions:
We strongly encourage using Private Vulnerability Reporting to disclose security issues to maintainers securely and privately.
- Navigate to the Security tab of the repository.
- Click the Report a vulnerability button.
- Provide all necessary details and a Safe Proof of Concept (PoC) that does not contain or distribute real malware. A safe PoC should trigger a harmless behavior, for example creating a folder/file on the desktop or showing logs.
Do not report disabling SIP (System Integrity Protection) or AMFI (Apple Mobile File Integrity) as vulnerabilities. These are necessary components for bypassing minimum system requirements and will be dismissed.
Note: If it is a fork of this project, then enabling the Report a vulnerability button is up to the maintainer of the fork. In case they don't enable this button, open an Issue with a [Vulnerability] tag. And forks may have different timeline on fixing certain vulnerabilities.