this post was submitted on 13 Aug 2026
196 points (99.5% liked)

Technology

87279 readers
4138 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
196
Terabytes of credentials leaked in massive supply-chain attack (arstechnica.com)
submitted 5 days ago by new_otters_raft@piefed.ca to c/technology@lemmy.world
23 comments fedilink hide all child comments
 

Terabytes worth of credentials, many belonging to the world's biggest and most sensitive organizations, have been exposed in a supply-chain attack on LiteLLM, an open source tool that streamlines A- driven software development. Microsoft, Amazon, Cisco, Samsung, and Salesforce are only a handful of the entities whose access secrets were exposed.

The revelation was posted on Tuesday and Wednesday by security firms CloudSEK and Hudson Rock. CloudSEK said it found cloud keys, repository tokens, SSH keys, Kubernetes secrets, package publishing credentials, environment variables, and AlI provider keys that could allow attackers to gain access to more than 2,500 organizations.

The credentials were extracted during a 40-minute window in March while the victims used compromised versions of LiteLLM downloaded from the package’s official location in the Python Package Index repository. Hudson Rock said it made the discovery after analyzing a 195TB file that it obtained. Neither firm identified the source of the information.

you are viewing a single comment's thread
view the rest of the comments
[–] douglasg14b@lemmy.world 5 points 4 days ago (1 children)

Our org is doing it better by just hiding the configuration from everyone else in the org, so no one can audit it anyways 🤦

Who knows how it's configured.

[–] python@lemmy.world 6 points 4 days ago

Have you ever pressed F12? We technically weren't allowed to see the config either, but LiteLLM literally returned a users password hash as part of the user data json in the version we were using. It was easy enough to see that it wasn't salted.
Another fun thing it does is that any user can see their entire teams token spend trough the network tab, even if they technically shouldn't be allowed to do that. Oh and LiteLLM had a CVSS score 9.9 vulnerability recently where any user with any sort of write privilege (including the "privilege" to change any of your own data, like your password) could just change their own role to admin 🤷

The pure incompetence of that software would be really funny if it wasn't such a pain in the ass to be the person who has to convince coworkers to rotate compromised credentials..