News for hackers. Stuff that matters.
Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by __mharrison__ on Friday March 27, 2026 @03:56PM (#47547437)
Love it! Let those pip users find the compromised packages for us uv users.
Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by bombcar on Friday March 27, 2026 @04:22PM (#47547747)
Until everyone waits 7 days to install everything so the compromise is discovered on the 8th day.

End result will be everyone runs COBOL only.

Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by gonzalohm on Friday March 27, 2026 @04:47PM (#47548046)
Or just scan all GitHub repos, find their .toml definition. Calculate the median and then add 7 days to that. That way you are always behind.
Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by zar1048576 on Friday March 27, 2026 @05:09PM (#47548279)
:-) That might not even be enough as I hear (but haven't verified) that Claude does a pretty good job of making sense out of legacy COBOL code!
Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by TacticalCoder on Friday March 27, 2026 @07:48PM (#47549892)
But not all project exploited in a supply chain attack get exploited on the same day.

So when project A gets pwned on day 1 and then, following the attack, project B gets pwned on day 3, if users wait 7 days to upgrade, then that leaves two days for the maintainers of project B to fix the mess: everybody shall have noticed on the 8th day that package A was exploited and that leaves time for project B (and the other projects depending on either A or B) to adapt / fix the mess.

As a sidenote during the first 7 days it could also happen that maintainers of project A notices the shenanigans.

Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by anthk on Friday March 27, 2026 @05:44PM (#47548704)
Or Forth with scientific library, bound to the constraints. Put some HTTP library on top and some easy HTML interface from a browser with no JS/CSS3 support at all. It will look rusty but unexploitable.

Enterprise computing with custom software will make a comeback to avoid these pitfalls. I depise OpenJDK/Mono because of patents but at least they come with complete defaults and a 'normal' install it's more than enough to ship a workable application for almost every OS. Ah, well, smartphones. Serious work is never done with these tools, even with high end tables. Maybe commercials/salespeople and that's it.

It's either that... or promoting reproducible environment with Guix everywhere. Your own Guix container, isolated, importing Pip/CPAN/CTAN/NPM/OPAM and who knows else into a manifest file and ready to ship anywhere, either as a Guix package, a Docker container (Guix can do that), a single DEB/RPM, an AppImage ready to launch on any modern GNU/Linux with a desktop and a lot more.

Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by dotancohen on Friday March 27, 2026 @10:46PM (#47551047)

  > Or Forth with scientific library, bound to the constraints. Put some HTTP library on top and some easy HTML interface from a browser with no JS/CSS3 support at all. It will look rusty but unexploitable.
Let this be a lesson to you youngsters that nothing in unexploitable.

Forth has no standard library for interfacing with SQLite or any other database. You're either using 8th or the C ABI. Therefore, you'll most likely be concatenating SQL queries. Are you disciplined enough to make that properly secure? Do you know all the intricacies?

Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by anthk on Saturday March 28, 2026 @12:43PM (#47556204)
GForth might have then for sure (Sqlite it's small and supported by even jimtcl) . Also, there's Factor, a Forth inspired language.
Re:Telnyx v4.87.1 and v4.87.2 are compromised by TeamPCP by dist-epoch on Friday March 27, 2026 @09:22PM (#47550552)
I'm already ahead of you. I'm using `exclude-newer = "8 days"`