|
| 1 | +While GitHub did not find sufficient information to determine a valid anti-circumvention claim, we determined that this takedown notice contains other valid copyright claim(s). |
| 2 | + |
| 3 | +--- |
| 4 | + |
| 5 | +**Are you the copyright holder or authorized to act on the copyright owner's behalf? If you are submitting this notice on behalf of a company, please be sure to use an email address on the company's domain. If you use a personal email address for a notice submitted on behalf of a company, we may not be able to process it.** |
| 6 | + |
| 7 | +Yes, I am authorized to act on the copyright owner's behalf. |
| 8 | + |
| 9 | +**Are you submitting a revised DMCA notice after GitHub Trust & Safety requested you make changes to your original notice?** |
| 10 | + |
| 11 | +No |
| 12 | + |
| 13 | +**Does your claim involve content on GitHub or npm.js?** |
| 14 | + |
| 15 | +GitHub |
| 16 | + |
| 17 | +**Please describe the nature of your copyright ownership or authorization to act on the owner's behalf.** |
| 18 | + |
| 19 | +This repo is a copy of Aera Technology Repo. We were notified of AWS that our keys were also added to this repo. |
| 20 | +Here is Aera private repo: [private] |
| 21 | +Here is the public repo: https://github.com/vladimir-j-fonseca/platform-iac |
| 22 | + |
| 23 | +**Please provide a detailed description of the original copyrighted work that has allegedly been infringed.** |
| 24 | + |
| 25 | +This is IAC code of Aera Technology, Inc. This code is nearly an exact copy of the original code. This also contained our private AWS token. AWS informed us that this key was made public: (April 14th, 2026) |
| 26 | +We have identified that the AWS access key [private], belonging to AWS Identity and Access Management (IAM) User externaldns, along with the corresponding secret key is publicly available online at: [private]. |
| 27 | +- Minor changes were made from the original repo, but the key and almost all code is the same. |
| 28 | + |
| 29 | +**If the original work referenced above is available online, please provide a URL.** |
| 30 | + |
| 31 | +Here is Aera private repo: [private] |
| 32 | +Here is the public repo: https://github.com/vladimir-j-fonseca/platform-iac |
| 33 | + |
| 34 | +**We ask that a DMCA takedown notice list every specific file in the repository that is infringing, unless the entire contents of the repository are infringing on your copyright. Please clearly state that the entire repository is infringing, OR provide the specific files within the repository you would like removed.** |
| 35 | + |
| 36 | +**Based on the above, I confirm that:** |
| 37 | + |
| 38 | +The entire repository is infringing |
| 39 | + |
| 40 | +**Identify the full repository URL that is infringing:** |
| 41 | + |
| 42 | +https://github.com/vladimir-j-fonseca/platform-iac |
| 43 | + |
| 44 | +**Do you claim to have any technological measures in place to control access to your copyrighted content? Please see our <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice#complaints-about-anti-circumvention-technology">Complaints about Anti-Circumvention Technology</a> if you are unsure.** |
| 45 | + |
| 46 | +Yes |
| 47 | + |
| 48 | +**What technological measures do you have in place and how do they effectively control access to your copyrighted material?** |
| 49 | + |
| 50 | +Aera technology has [private] with SSO and MFA. Strict access controls and many other controls are in place for access to Aera [private]. |
| 51 | + |
| 52 | +**How is the accused project designed to circumvent your technological protection measures?** |
| 53 | + |
| 54 | +This may be a former employee who had a copy of this repo when he was an employee. Based on the name of the org that has the repo. |
| 55 | + |
| 56 | +**If you are reporting an allegedly infringing fork, please note that each fork is a distinct repository and <i>must be identified separately</i>. Please read more about <a href="https://docs.github.com/articles/dmca-takedown-policy#b-what-about-forks-or-whats-a-fork">forks.</a> As forks may often contain different material than in the parent repository, if you believe any of the repositories or files in the forks are infringing, please list each fork URL below:** |
| 57 | + |
| 58 | +**Is the work licensed under an open source license?** |
| 59 | + |
| 60 | +No |
| 61 | + |
| 62 | +**What would be the best solution for the alleged infringement?** |
| 63 | + |
| 64 | +Reported content must be removed |
| 65 | + |
| 66 | +**Do you have the alleged infringer’s contact information? If so, please provide it.** |
| 67 | + |
| 68 | +No, but we can get it. But we don't know for sure who created this Org / Repo. The name matches an ex employee. |
| 69 | + |
| 70 | +**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.** |
| 71 | + |
| 72 | +**I have taken <a href="https://www.lumendatabase.org/topics/22">fair use</a> into consideration.** |
| 73 | + |
| 74 | +**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.** |
| 75 | + |
| 76 | +**I have read and understand GitHub's <a href="https://docs.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/">Guide to Submitting a DMCA Takedown Notice</a>.** |
| 77 | + |
| 78 | +**So that we can get back to you, please provide either your telephone number or physical address.** |
| 79 | + |
| 80 | +[private] |
| 81 | + |
| 82 | +**Please type your full name for your signature.** |
| 83 | + |
| 84 | +[private] |
0 commit comments