For the next few months, we are looking at frequent discoveries of long-standing bugs - competent code auditing has gotten cheap and abundant. This carries a few consequences:

There is a recurring info I hear from vendors that there is often a first discovery of a vulnerability by AI and suddenly one or two weeks later lots of collisions come in. In this case the PHP bugs were first discovered 5th August and then rediscovered 2 weeks later

The amount of scavengers that come out just as a new vulnerability is disclosed is insane in the age of AI...

this is such an insane thing to admit. imagine the security of your network is based on the outputs of dozens of independent dumb llms that no person will be able to understand or safely extend in the future

Finally our HP printer will accept 3rd party ink! Thanx @morluto github.com/morluto/rea

PSA the ledger incident isn't limited to Asia This is a device purchased in store from an official reseller in Europe (a legitimate device doesn't have any of these cables as can be seen in picture 2) This even seems to be an old version of the 'spy implant' even though the device was purchased a couple of weeks ago. The newer versions usually hide the implant by the screen so it's easier to miss What's interesting is that this compromised ledger never transfered funds to an exploiter. Either the device didn't work or they were waiting for a more widespread usage of the comprised devices? If you own a ledger that didn't directly come from the ledger online store make sure to not just rely on the software genuinely check by ledger but to actually open up the ledger yourself to make sure its original, again there are reported cases in Asia, south America and now Europe as well. @MagicalTux made some useful videos on how to open the ledger and what to look for.