🫂"hugs from TeamPCP."
We're now 47 days and three rounds deep into the Checkmarx incident -- and this time TeamPCP left a message for victims in `~/hugs_from_teamPCP.txt`
Things appear mitigated, but waiting to see if rotation was a bit more atomic this time 🤞
List of most popular/active public repos on GitHub - April edition:
- @openclaw hype is over?
- @Microsoft GenAI tutorials are back to the first place
- April normalized to AI models and established learning
resources
Preliminary exploit detections for Copy Fail (CVE-2026-31431) based on our tests (these work best in combination):
1. "NET: Registered PF_ALG protocol family" in kern.log & syslog
2. curl for "copy[.]fail/exp" (if attacker is lazy)
3. su record without invoking user in auth.log
Patch your Linux boxes!
https://t.co/VWOUDbLAn2 is a trivially exploitable logic bug in Linux, reachable on all major distros released in the last 9 years. A small, portable python script gets root on all platforms.
Found by the teams at @theori_io and @xint_official
More details below
https://t.co/9f6T96PvPX
Fork commits keep showing up in supply chain attacks (tj-actions, reviewdog, TeamPCP).
But, I keep seeing incorrect explanations in incident threads/blogs
So I built a microsite to cut through the confusion
🔗in🧵
Monthly list of most popular/active public repos on GitHub:
- @openclaw keeps the first place (although its half pace comparing to February)
- Rise of the personal claude skills and harnesses over official anthropics/skills
- karpathy/autoresearch - fast-breaker
Turns out # of forks is a great metric of repo popularity. Here is the most popular/forked repos of Feb 2026. Of course, #OpenClaw is leading the pack:
@GrahamHelton3 This is great research @GrahamHelton3 . Couldn't find it in the blog - is the command execution possible with node/proxy:list or node/proxy:watch?
UPDATE: Shai-Hulud 2.0 has a long tail, and it may have led to $7M in crypto theft.
Earlier today, our update laid out how sha1-hulud may have caused the Trust Wallet incident.
Trust Wallet just announced the same conclusion 📷Read our analysis >> https://t.co/nYIaOcueNB
With #shaihulud2 refuses to die with the long tale of infections (117 new compromised machines in the last 72 hours, most of them form @Cursor IDE), all @github has to do is disable the gho_ tokens of the super-spreaders (last 2 active spreaders are Cpreet and moh-abed).
🪱sharing more on sha1-hulud w/@sshaybbc
* 2 packages == ~60% of infections
* 400k unique secrets in truffleSecrets.jsons, only 2.5% verified, & the majority of those short lived JWTs for GitHub Actions!
* 3/4 of impacted workloads were CI/CD, 1/4 were users
🔗below
🤖 65% of Forbes AI 50 companies leaked secrets on GitHub. @sshaybbc revealed how AI speed without security = leaks waiting to happen.
Full Wiz Research report 👉
https://t.co/kmamDrkIo3
@adnanthekhan At the end we need an attribution to stop this crazy attack sequence, I'd love to see more publications around the actor behaviour and to see GH doing more.
@adnanthekhan No cloud impact so far, but the abuse of the cloud access is an incremental evolution step that this actor seems to demonstrate with every attack. Given the likely pool of cloud creds they have now I won't be surprised...