Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Blockly name used to store obfuscated/stolen/license violating code #8712

Open
blepping opened this issue Dec 28, 2024 · 3 comments
Open

Comments

@blepping
Copy link

Link: https://github.com/lllyasviel/google_blockly_prototypes/tree/main/forge
This contains obfuscated code stolen from another repo in violation of its license. See: lllyasviel/stable-diffusion-webui-forge#2151
At the source where it's used, it's emitting log messages like "initializing google blockly", while in fact it is just rehydrating this stolen, obfuscated code.
In essence, it's using Google's name and reputation as a shield to make people less likely to investigate.

Right now, it seems like this is just used as a method to avoid crediting/adhering to the other project's license but in the future it could be used to deliver malicious/harmful code to the end user - while purporting to be related to Google Blockly.

@blepping blepping changed the title Google Blockly name used to store obfuscated/stole/license violating code Google Blockly name used to store obfuscated/stolen/license violating code Dec 28, 2024
@parsee-mizuhashi
Copy link

As the creator of the aforementioned PR, yes, I can confirm that lllyasviel is using blockly's name to disguise obfuscated & stolen code. There is a possibility the code may also hide malicious code, due to some out of place imports.

@rachel-fenichel
Copy link
Collaborator

Thanks for reporting this; we're taking a look.

@blepping
Copy link
Author

@rachel-fenichel I hadn't really been following the linked pull since it's been a while but it appears there have been some recent developments. A different person with commit access removed the part was loading the obfuscated/stolen code in webui-forge. The repo hosting that code still remains unchanged and it's certainly possible that the main repo owner of webui-forge will revert those changes and add it back. (Also not sure if there might be anything else referencing it out there, even if webui-forge doesn't.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants