🚨🚨🚨 ALERTE SÉCURITÉ MAXIMALE ! Python est compromis.
🔸 Mettez immédiatement pip à la version 26.2.2 ou plus.
🔸 Dans chaque projet Python (chaque venv) : python -m pip install --upgrade pip
🔸 uv : uv self update (0.13.4 ou plus)
🔸 Mettez aussi à jour les certificats du système (apt / dnf upgrade ca-certificates) et vos images Docker
pip install est compromis.
L'autorité indienne eMudhra (emSign), qui signe les « passeports » prouvant qu'un site est bien celui qu'il prétend être, utilisait des clés secrètes ridiculement faibles : 8 clés, toutes inférieures à 256. L'une valait 4. Autrement dit, n'importe qui peut fabriquer un faux passeport valide pour n'importe quel site.
Le risque pour Python : quelqu'un sur ton réseau (wifi public, FAI, État) se fait passer pour https://t.co/KxkevWMTiB, et ton « pip install » télécharge un paquet piégé sans aucune alerte. Aucune attaque n'a été signalée pour l'instant, mais c'est trivial à faire.
Un paquet piégé peut installer n'importe quoi. Porte dérobée, virus, vol d'informations en tout genre.
La situation est terrifiante !
Rien que dans l'écosystème Python, chaque installation de CPython, chaque venv, uv, tout est exposé.
Et je ne vous parle même pas de npm, pnpm, yarn, Go, Rust.
Ma stratégie de sécurité 2026 : rester chez moi et ne me connecter à Internet que depuis un FAI de confiance.
C'est quand il y a de la mer qu'on reconnaît les vrais marins...
We discovered a sophisticated recording device that was hidden inside one of our offices. We used our models to understand the device and where it had come from, identifying that a specific employee had planted it a few days earlier. We referred the matter to the FBI, and we’re grateful to the agents and prosecutors who moved quickly to make an arrest. The FBI’s investigation is ongoing and we will continue to support their work.
At this time, we have no indications of this individual inappropriately accessing or exfiltrating model weights, source code, or customer data. The employee was terminated.
We take protecting our technology, data, and people seriously, and as a matter of national importance. Our security program is designed to protect against a wide range of threat actors, from insider risks to cybercriminals to nation states, and this case is an example of how AI can help address these sophisticated security threats.
You can finally close your laptop now and your agents will keep working.
Codex cloud environments are here.
Reusable environments mean less setup and faster starts, with your repo, dependencies, scripts, and settings already in place.
Dots are here!
A new way to use AI that works 24/7 for you; get more of your time and attention back to work at a higher level.
https://t.co/Kp4fPSGUTT
How is Jev so much faster than an LLM?
It's not about how the model is trained - it's the inference technique.
In fact, you can modify an inference engine to provide a performant Jev-like API with any open-weight LLM.
Say you are trying to ask N multiple choice questions in parallel.
In standard text generation, you decode tokens one at a time to generate a JSON representing those properties, and then parse the JSON.
In a Jev-like system, what you can do is:
- Label choices for each property 1,2,3,...
- Prefill the shared information (output shape and other context)
- Fork this inference context for each property, re-using that cached prefill
- Add an individual question to each parallel context
- Look at the logits (token probabilities) for each one, constrained to the valid choice labels
- Map the labels back to the choice values. Include the softmax of the logit itself to get a combined choice+confidence score
This means you decode one time in parallel across all questions, instead of one at a time - so the efficiency gains roughly scale with the number of questions per request (until compute is saturated).
So what makes Jev's model unique? It's because they train a small model to perform well in this specific inference setting - improving both cost and capability compared to a non-specialized model.
Ultimately though, if you have a use case Jev would be good for, you could do it with open-weight models too!
(Some speculation made here about how Jev's engine might work, but this is one way you could get similar performance)
A 744 billion parameter AI model just ran on a machine with 25GB of RAM.
No graphics card.
The tool is called colibri.
GLM-5.2 is a mixture-of-experts model. It contains 744 billion parameters but only about 40 billion wake up for each token.
colibri keeps the 9.9GB core in memory.
The remaining 370GB sits on an SSD. As the model writes, colibri pulls in only the tiny group of experts needed for that token.
→ Pure C
→ Zero runtime dependencies
→ 25GB RAM
→ Zero graphics cards
→ The full model stays on your machine
The catch is brutal.
A cold token can require 11GB of disk reads, so output crawls at roughly one token every 10 to 20 seconds. You will not replace ChatGPT with this tomorrow.
But colibri cracks the assumption that the whole model must fit in memory before it can run.
100% open source.
https://t.co/dSm86eRWCj
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
one very cool development with gpt 6 astra is that you can change reasoning effort mid-convo without invalidating the cache. start with astra light (roughly equivalent to sol medium), then jack the thinking effort up if you see the task can benefit from more, all without worrying about having to rewrite the complete context cache.
@evisdrenova Evis, Great share. Separately, I closely follow professional in our space by the name of Sebastian R. would like to know your opinion regarding this post : https://t.co/KD55xWJXMU?
We unfortunately have decided that we cannot continue providing access to our models through Cursor and are ending our partnership. It boils down to trust and we’ve asked that this takes effect on November 12 to give you some time to plan.
Many have used the GPT models through Cursor and here are options we know should work in the future:
- We will continue to allow using your own OpenAI API key and similarly will continue to provide access through our IDE extensions for Cursor.
- We will keep working with the broadest range of tools and harnesses, some of which are OSS, but also many many closed-source ones.
We are as committed as ever to continue supporting developers and the flourishing ecosystem of tools, harnesses and products. We will also continue to invest in our own open-source initiatives and believe in broad optionality for developers.
You can read more about our decision in the blog:
https://t.co/Oj76Bkc2KX