As many of you know, I am fascinated by #AI/#ML. I don't have a #mentor to work with so I'm often left to my own devices. The repository below is an example of how I "lead myself" when a mentor isn't available. Read this thread for details 🧵
github.com/SecretSourceWeb/G…
Introducing Project Glasswing: an urgent initiative to help secure the world’s most critical software.
It’s powered by our newest frontier model, Claude Mythos Preview, which can find software vulnerabilities better than all but the most skilled humans.
anthropic.com/glasswing
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.
LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below
I'm working on a personal project that requires the creation of hundreds of selfies. I compared 20 models and produced samples for each using the same prompt. chicagoitsystems.com/ai-mode…
I would love your feedback!
Ted Stresen-Reuter
I understand that the JWT must be sent with the request. As the call to the Edge Function is initialized by the cron job, does that mean it is operating as the `postgres` role? Don't you think _some_ check should be in place so that anon roles aren't initializing updates?
At the height of One Million Checkboxes's popularity I thought I'd been hacked. A few hours later I was tearing up, extraordinarily proud of some brilliant teens.
A thread about my favorite story from running OMCB....
I made a website. it's called "one million checkboxes dot com". it has one million checkboxes on it.
checking a box checks it for everyone.
that's it. have fun!
There should be as little friction as possible between your thoughts and their manifestations in code.
I cannot stress the importance of being able to do this enough. Make this your priority.
It sounds ridiculous to say that but I can’t tell you how many new programmers I’ve met who can’t do this, and it SLOWS THEM DOWN SIGNIFICANTLY. The keyboard is your main tool, your instrument. Learn how to play it perfectly.
#Coding 1 of 10
LEARN TO TYPE WITH ALL 10 FINGERS AND WITHOUT LOOKING!
More than any other thing you should be able to type with all 10 fingers and without looking at your keyboard.