Added 2025/06/2025-06-18-vmprotect.md

[dmca-sync-bot]

This is an automated pull request to sync changes from upstream repository.

Diff summary:

A 2025/06/2025-06-18-vmprotect.md

[Copilot]

Pull Request Overview

This PR adds a new DMCA takedown notice file for VMProtect, detailing the alleged copyright infringement and the URLs of repositories to remove.

• Introduces 2025-06-18-vmprotect.md with the full takedown notice content
• Specifies infringing repository URLs and fork URLs for VMProtect content

Comments suppressed due to low confidence (1)

2025/06/2025-06-18-vmprotect.md:23

• [nitpick] Rephrase this sentence for clarity. For example: "Individuals have published VMProtect's source code and compiled binaries online, and subsequently many GitHub users have added these materials to their own repositories."

I have read and understand GitHub's Guide to Filing a DMCA Notice. I'm one of the [private] of VMProtect (https://vmpsoft.com). Someone has published of our VMProtect's sources/compiled binaries on the Internet and after that many of Github's users published these sources/compiled binaries in own repositories. Based on the representative number of forks I have reviewed, I believe that all of the forks are infringing to the same extent as the parent repository.  

[Copilot]

Correct capitalization of the GitHub trademark: use "GitHub's users".

Suggested change

I have read and understand GitHub's Guide to Filing a DMCA Notice. I'm one of the [private] of VMProtect (https://vmpsoft.com). Someone has published of our VMProtect's sources/compiled binaries on the Internet and after that many of Github's users published these sources/compiled binaries in own repositories. Based on the representative number of forks I have reviewed, I believe that all of the forks are infringing to the same extent as the parent repository.

I have read and understand GitHub's Guide to Filing a DMCA Notice. I'm one of the [private] of VMProtect (https://vmpsoft.com). Someone has published of our VMProtect's sources/compiled binaries on the Internet and after that many of GitHub's users published these sources/compiled binaries in own repositories. Based on the representative number of forks I have reviewed, I believe that all of the forks are infringing to the same extent as the parent repository.