Hello everyone!
This is my private account, Welcome!
if you know me, congratulations on finding this incredibly poor attempt at obfuscation with fantastic OSINT skills :V
Hack COMPLETE! Hi everyone, it's me, Diana! I'll be posting here for a little bit! I'm so excited to learn about Earth from you all. Let's play together, okay?
Oh dear, what a shocker, pushing and forcing an untested, unproven system to REPLACE THE ENTIRE FUCKING CORE UTILS, turned out to be a security concern and issue
Ubuntu Hired Security Research Firm After Rust Re-writes Raised "Serious Concerns"
With the release of Ubuntu 26.04 (Long Term Support), Ubuntu is revealing massive security and ship-ability issues with the Rust-based, GNU Coreutils replacements.
๐ WARNING: Bitwarden CLI was compromised in a supply chain attack.
@bitwarden/[email protected] included malicious code after attackers hijacked GitHub Actions, stole secrets, and pushed a tampered version to npm.
๐ Learn how the attack worked โ https://t.co/xqqJ7a9REL
๐ WARNING: Bitwarden CLI was compromised in a supply chain attack.
@bitwarden/[email protected] included malicious code after attackers hijacked GitHub Actions, stole secrets, and pushed a tampered version to npm.
๐ Learn how the attack worked โ https://t.co/xqqJ7a9REL
Software horror: litellm PyPI supply chain attack.
Simple `pip install litellm` was enough to exfiltrate SSH keys, AWS/GCP/Azure creds, Kubernetes configs, git credentials, env vars (all your API keys), shell history, crypto wallets, SSL private keys, CI/CD secrets, database passwords.
LiteLLM itself has 97 million downloads per month which is already terrible, but much worse, the contagion spreads to any project that depends on litellm. For example, if you did `pip install dspy` (which depended on litellm>=1.64.0), you'd also be pwnd. Same for any other large project that depended on litellm.
Afaict the poisoned version was up for only less than ~1 hour. The attack had a bug which led to its discovery - Callum McMahon was using an MCP plugin inside Cursor that pulled in litellm as a transitive dependency. When litellm 1.82.8 installed, their machine ran out of RAM and crashed. So if the attacker didn't vibe code this attack it could have been undetected for many days or weeks.
Supply chain attacks like this are basically the scariest thing imaginable in modern software. Every time you install any depedency you could be pulling in a poisoned package anywhere deep inside its entire depedency tree. This is especially risky with large projects that might have lots and lots of dependencies. The credentials that do get stolen in each attack can then be used to take over more accounts and compromise more packages.
Classical software engineering would have you believe that dependencies are good (we're building pyramids from bricks), but imo this has to be re-evaluated, and it's why I've been so growingly averse to them, preferring to use LLMs to "yoink" functionality when it's simple enough and possible.
I'm getting hit with anxiety/panic from just the lack of agency and control I have with everything, can windows please stop doing things...on its own...for...JUST 1 SECOND???????
MICROSOFT WINDOWS FUCKING 11, WHAT IN THE EVER LIVING FUCK
FIRST YOU RESTART IN THE MORNING, NOW YOU RESTART - IN THE MIDDLE OF THE EVENING WHEN I AM USING?????????????????
MICROSOFT WINDOWS FUCKING 11, WHAT IN THE EVER LIVING FUCK
FIRST YOU RESTART IN THE MORNING, NOW YOU RESTART - IN THE MIDDLE OF THE EVENING WHEN I AM USING?????????????????