security : limiting write access to the repository/organization #20954
Replies: 17 comments 37 replies
-
|
Looks like I've been affected by the permissions change. I can't trigger CIs or merge PRs as before. Can you double check my permissions? |
Beta Was this translation helpful? Give feedback.
-
|
Same here, no more write I only use Python in disposable/isolated/rootless containers. These environments have no access to GitHub or any other service. and no LiteLLM here (I use llama.cpp :) |
Beta Was this translation helpful? Give feedback.
-
|
Same, relogged off and on to GH account but no change. |
Beta Was this translation helpful? Give feedback.
-
|
I have never manually installed or directly used LiteLLM. When I do local language model inference I typically do it via the llama.cpp stack. The last time I installed any LLM-related Python packages was in the context of vLLM about a month ago (which to my understanding does not come with LiteLLM preinstalled and I would think my usage predates when this attack was added). I am not seeing an installation of LiteLLM in any of my relevant Python environments. |
Beta Was this translation helpful? Give feedback.
-
|
Confirm that I no longer have write permission. I ran |
Beta Was this translation helpful? Give feedback.
-
|
So it seems that LiteLLM got infected via their CI. Do we have our CI set up correctly in the sense that any tokens we use have the minimum possible scope so that even if they somehow get stolen this would not compromise anything else? |
Beta Was this translation helpful? Give feedback.
-
|
I have never knowingly installed litellm, i dont have very many venvs either, none of which include any affected version. |
Beta Was this translation helpful? Give feedback.
-
|
All clean over here. Never used litellm but double-checked just in case. |
Beta Was this translation helpful? Give feedback.
-
|
No trace of LiteLLM, though I leave nothing to harvest anyway. :) |
Beta Was this translation helpful? Give feedback.
-
|
No LiteLLM to be found, anywhere. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Vibecoded PowerShell script for Windows users (probably only me): No installed versions of LiteLLM in any of my virtualenvs. |
Beta Was this translation helpful? Give feedback.
-
|
No litellm for me |
Beta Was this translation helpful? Give feedback.
-
|
No litellm found for me. |
Beta Was this translation helpful? Give feedback.
-
|
No litellm on my system! |
Beta Was this translation helpful? Give feedback.
-
|
The write access is now restored. I've updated the OP of this thread with some action items. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think I've any write access but for what is worth, no litellm here neither |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
@ggml-org/core @ggml-org/maintainers @ggml-org/hf Heads up, as a security precaution to the developing supply-chain attack of the LiteLLM package (BerriAI/litellm#24512), I have disabled the write permission of all existing collaborators. Please double-check that you have not been affected by the attack.
Check script:
Update
Taking some extra measures to improve the security of the project:
Disabled some of the self-hosted runners until they are properly sandboxed
Write access of maintainers is restored. Increased "Required approvals" for PRs from 1 to 2:
TODOs
masterbranch to a newreleasebranch. New releases will be triggered manually, after an audit by the maintainersBeta Was this translation helpful? Give feedback.
All reactions