Mercor says it was hit by cyberattack tied to compromise LiteLLM
45 points by jackson-mcd 2 days ago | 15 comments
aservus 3 hours ago
This is a good reminder that any tool handling sensitive data — even internal ones — needs to be transparent about where data goes. The assumption that SaaS tools protect your data is getting harder to defend.
replylukewarm707 2 hours ago
I use llms to read the privacy policies that are too long to read. They guarantee almost nothing, unless you go out of your way to get an sla
replyashishb 4 hours ago
[flagged]
replylmc 3 hours ago
Docker is not a strong security boundary and shouldn't be used to sandbox like this
replyhttps://cloud.google.com/blog/products/gcp/exploring-contain...
EE84M3i 2 hours ago
Confusingly, Docker now has a product called "Docker Sandboxes" [1] which claims to use "microVMs" for sandboxing (separate VM per "agent"), so it's unclear to me if those rely on the same trust boundaries that traditional docker containers do (namespaces, seccomp, capabilities, etc), or if they expect the VM to be the trust boundary.
replyashishb 3 hours ago
Compared to what?
Which one is superior?
replyRunning 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.
notachatbot123 3 hours ago
[flagged]
reply
This 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