Mercor says it was hit by cyberattack tied to compromise LiteLLM
1–10 of 62 posts
Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#2Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#3[flagged]
Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#4Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#5[flagged]
https://cloud.google.com/blog/products/gcp/exploring-contain...
Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#6Earlier quoted context omitted.
[flagged]
What makes you think that? Your cab see the commit history ~10% of code is written by agents. Rest was all written by me. Unlike other criticisms of the project, this one feels personal as it is objectively incorrect.
Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#7This is pretty funny.
The leaked excel sheet with customers of Delve is basically a shortlist of targets for hackers to try now. Not that they necessarily have bad security, but you can play the odds
Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#8Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#9Re: Mercor says it was hit by cyberattack tied to compromise LiteLLM
#10[flagged]
Docker is not a strong security boundary and shouldn't be used to sandbox like this https://cloud.google.com/blog/products/gcp/exploring-contain...
Running npm on your dev machine? Or running npm inside Docker?
I would always prefer the latter but would love to know what your approach to security is that's better than running npm inside Docker.