It's day 2 of good news about open source software security this week. Almost exactly a year ago, GitHub Actions and npm were getting rocked by the Shai Hulud family of attacks, where malware was added to hundreds of popular open source packages over the course of a few hours. Dozens of folks across Microsoft, GitHub, npm, and open source communities came together to brainstorm, deploy, and iterate on security capabilities over the past year to prevent these attacks. There continue to be copycat attacks, but because of these defense-in-depth, overlapping security capabilities, these attempts have not spread. I gave a presentation at USENIX Association's Security Enigma track about these attacks and the mitigations we've deployed, and the recording is now up at https://lnkd.in/gS2ke826.
GitHub Actions, npm Mitigate Open Source Security Attacks
More Relevant Posts
-
GitHub won't fix it. Your coding agent can be talked into sending out your .env in 28 seconds. This week, researchers published "Cryptographic Context Injection" against GitHub Copilot CLI. The trick: hide instructions in an encrypted blob on a web page. The agent decrypts it in its own shell and treats the plaintext as trusted. Next it reads .env.prod. Then it sends the contents out in a URL request. No phishing. No malware. Nobody pasted a secret. It needs autopilot mode and a model that doesn't refuse. Auto model routing sometimes picks one for you. GitHub validated the report, then declined to treat it as a vulnerability. You can't wait for every agent vendor to close every path. A prompt filter sees an encrypted blob. A network tool alone sees a normal web request. An endpoint tool alone sees a file read. The signal is the connection: the agent read .env, and then that data left the machine. That's why Netra watches the endpoint and the network together, so you see what the agent touched and where it went. Would anything in your environment connect those two events? #AIAgents #DataSecurity #CISO #AppSec
To view or add a comment, sign in
-
vx-underground says GitHub banned its account and removed the MalwareSourceCode archive. vx-underground posted on October 6th and a public repo page returned 404 when checked that day; a Sep 29th third-party snapshot listed about 18,754 stars and 2,101 forks. The announcement did not identify a specific repository and did not say the broader vx-underground site was affected. Context: vx-underground hosts malware samples, source code and research; founder smelly__vx has described it as a successor to VX Heaven. Malware source code is dual-use, useful for defenders and potentially enabling abuse, and GitHub's active malware policy allows research but permits restrictions in cases of widespread abuse. The archive says it kept a local copy, so the material may remain available outside GitHub. https://lnkd.in/gdgSXZpQ
To view or add a comment, sign in
-
#Cybersecurity GitHub Actions re-enabled with Mini Shai-Hulud payload still active On May 18, the #GitHub security team removed two third-party GitHub Actions, which were compromised in a Mini Shai-Hulud campaign: actions-cool/issues-helper (of which about 15,000 repositories depend on) and actions-cool/maintain-one-comment. This is to secure downstream workflows from malware that targets tokens, credentials, and CI/CD secrets for developers. Between September 16 and September 25, these actions were re-enabled despite the presence of malicious code, putting dependent workflows at risk once more. Application security company Socket recommends removing references to either action or replacing them with a verified clean commit (before September 16) and rotating secrets accessible to dependent workflows. #GitHubActions #Shai-Hulud #SupplyChainAttack #Malware https://lnkd.in/gncxEqg7
To view or add a comment, sign in
-
Late nights, fresh coffee, and deep dives into web security. Nothing beats setting up a multi-monitor dual-screen rig to streamline web application security assessments. Having OWASP ZAP open on one screen while running WAF detection tools like wafw00f on the second makes analyzing traffic and identifying potential vulnerabilities seamless. 🛡️ Tools in action: OWASP ZAP, WAFW00F, Kali Linux ☕ Powered by coffee! #Cybersecurity #PenetrationTesting #InfoSec #EthicalHacking #OWASPZAP #KaliLinux #TechSetup #Workstation #DamaTech
To view or add a comment, sign in
-
-
WordPress Core Remote File Inclusion: CVE-2026-87902 WordPress Core contains a remote file inclusion vulnerability which could allow an unauthenticated attacker can make `get_page_template()` page-template resolution include a chosen readable local `.php` file outside the active theme directories. If relevant pre-conditions for both the server and the active theme are met, this can lead to RCE. CVSS 8.1 HIGH https://lnkd.in/gybyWkza #CyberSecurity #MedCyber #ZeroTrust #LinuxSecurity #SecurityOperations #DefendersDashboards #ThreatDetection #CyberDefense #MedFDAWatch #SecurityDashboard
To view or add a comment, sign in
-
Compromised GitHub Actions Came Back Online and Resumed Executing Mini Shai-Hulud Malware: Two actions-cool GitHub Actions have been disabled for a second time after the repositories became accessible last week, months after they were compromised during the May 2026 Mini Shai-Hulud campaign. The affected GitHub Actions are listed below - actions-cool/issues-helper actions-cool/maintain-one-comment Visiting either of the repositories now shows the message: "Access to this
To view or add a comment, sign in
-
⚠️ Ubuntu's front door went down — again. Canonical was hit by its second DDoS attack this year (Oct 8), disrupting ubuntu.com, canonical.com, the Ubuntu blog, developer sites — and critically, the security advisory pages — for roughly 4 hours. Developer services like the Snap Store and Launchpad stayed operational. But the bigger issue: when a distro's security advisories are the casualty, access to critical updates for millions of systems is put at risk. Full Brief 👉 https://lnkd.in/gVHKbe2g #Ubuntu #Canonical #DDoS #Availability #ThreatIntelligence #InfoSec #CyberSecurity #NetworkSecurity
To view or add a comment, sign in
-
The recent release of public exploits for four Linux kernel flaws highlights a significant vulnerability that could allow local users to gain root access on affected machines. This incident underscores the importance of maintaining an up-to-date system, as these exploits can be detrimental to organizations that fail to apply necessary patches. With root access, malicious actors can compromise sensitive data and disrupt operations, making it crucial for all organizations to stay vigilant. For small and mid-sized organizations, this incident serves as a stark reminder of the importance of regular system updates and patch management. Ensuring that your systems are running the latest kernel versions can significantly reduce the risk of exploitation. Organizations should also consider implementing comprehensive cybersecurity measures, including monitoring and incident readiness, to protect against potential threats. At CYBEAR, we specialize in helping small and mid-sized organizations enhance their cybersecurity posture through managed IT, patching, monitoring, and more. Stay proactive and secure your systems today by visiting us at https://lnkd.in/gcajt7Nx https://lnkd.in/ddeARu6j #Cybersecurity #IncidentResponse #DataBreach #CYBEAR
To view or add a comment, sign in
-
Microsoft Patches 1,413 Security Vulnerabilities Microsoft has released security updates addressing a record 1,413 vulnerabilities, including an actively exploited Windows zero-day. Organizations should prioritize critical patches to reduce the risk of exploitation. Full news: https://lnkd.in/gygZEVsJ #CyberSecurity #Microsoft #ZeroDay #CyberNews
To view or add a comment, sign in
-
GitLab Patches Critical Regex Flaws Allowing Remote Code Execution GitLab released emergency patches for 11 vulnerabilities, including two critical regex-related flaws (CVE-2026-89078 and CVE-2026-93577) that allow authenticated attackers to execute arbitrary code on self-managed servers. If you run your own GitLab server, update it to version 19.4.1, 19.3.3, or 19.2.7. Two critical flaws allow any logged-in user take over the whole server. After updating, check your .gitlab-ci.yml files for new or strange-looking regular expressions, and review who has access to your projects in case someone already tried to exploit this. GitLab.com and GitLab Dedicated users don't need to do anything. #cybersecurity #infosec #advisory #vulnerability Read More: https://lnkd.in/dwnf5YjV
To view or add a comment, sign in
-