dmca/2023-05-19-evozi.md at master

github/dmca

Fork 0

mirror of https://github.com/github/dmca.git synced 2025-06-18 17:05:41 -04:00

dmca-sync-bot 54a19a25d4 Process DMCA request

2023-05-23 18:05:37 +00:00

7.9 KiB

Raw Permalink Blame History

Before disabling any content in relation to this takedown notice, GitHub

contacted the owners of the affected repositories to give them an opportunity to make changes.
provided information on how to submit a DMCA Counter Notice.
offered to connect the owners of the affected repositories with legal resources as part of our commitment to standing up for developers.

To learn about when and why GitHub may process some notices this way, please visit our README.

Are you the copyright holder or authorized to act on the copyright owner's behalf?

Yes, I am the copyright holder.

Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?

Does your claim involve content on GitHub or npm.js?

GitHub

Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.

I'm fully authorized to act on behalf of Evozi, the copyright owner of the work described below.

Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.

It’s a set of tools that allow to extract and decrypt several proprietary formats found in our app. Since the file format is not public, it’s based upon reverse engineering and enable circumvention of Evozi apps

What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository’s URL.

Repo:
https://github.com/PANCHO7532B/HCDecryptor
Forks:
https://github.com/1eo1/HCDecryptor
https://github.com/Blacker0101/HCDecryptor
https://github.com/DetektifNeet/HCDecryptor
https://github.com/karlicaca/HCDecryptor
https://github.com/ROKERPOWER/HCDecryptor-2

Repo:
https://github.com/flmorse/hcdrill-tg
Forks:
https://github.com/5l1v3r1/hcdrill-tg
https://github.com/bagus184/hcdrill-tg
https://github.com/delbyabreu/hcdrill-tg

Repo:
https://github.com/tools-inet/hctools
Forks:
https://github.com/1eo1/hctools

Repo:
https://github.com/rifkimubarok/ehi-unlock
Forks:
https://github.com/hermesthecat/ehi-unlock
https://github.com/noobconner21/ehi-unlock
https://github.com/lakshan17/ehi-unlock

Repo:
https://github.com/ikuvamzz/ehi-unlock
Forks:
https://github.com/666lucy999/ehi-unlock
https://github.com/lakshan17/ehi-unlock-1

Repo:
https://github.com/noobconner21/Http-Injector-Decrypt-Script
Forks:
https://github.com/Buddhi2022/Http-Injector-Decrypt-Script
https://github.com/deepx223/Http-Injector-Decrypt-Script
https://github.com/wade231/Http-Injector-Decrypt-Script

Repo:
https://github.com/alanwalker98/Http-Injector-Decrypt-Script
Forks:
https://github.com/All-Collection/Http-Injector-Decrypt-Script
https://github.com/deyvisml/Http-Injector-Decrypt-Script

Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our Complaints about Anti-Circumvention Technology if you are unsure.

Yes

What technological measures do you have in place and how do they effectively control access to your copyrighted material?

We have used a [private] to protect the app, besides that the app also used [private] for anti hooking and memory dumping. Config file created by the app also being proprietary format and only readable by our own app.

How is the accused project designed to circumvent your technological protection measures?

It violates our technological measures by decompiling/hooking the app, since our app allow user to create a config file which is using our proprietary format which contain sensitive information in it. Based on the illegal decompiling that they created an automated tool to decrypt our proprietary file.

This GitHub repository violates a section of 17 U.S.C. § 1201 which is a part of the Digital Millennium Copyright Act.

Have you searched for any forks of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.

Yes. Take down all of the repository's forks.

Is the work licensed under an open source license?

What would be the best solution for the alleged infringement?

Other Change

Describe the change.

The repository must be taken down.

Do you have the alleged infringer’s contact information? If so, please provide it.

No.

I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law.

I have taken fair use into consideration.

I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.

I have read and understand GitHub's Guide to Submitting a DMCA Takedown Notice.

So that we can get back to you, please provide either your telephone number or physical address.

[private]

Please type your full legal name below to sign this request.

[private]

7.9 KiB Raw Permalink Blame History Unescape Escape

7.9 KiB

Raw Permalink Blame History