< ciso
brief />
Tag Banner

All news with #github tag

166 articles

WinGet Flaw Let One Pull Request Leak Moderator Tokens

πŸ” Researchers at Cycode found a now patched, zero-click supply chain flaw in Microsoft's WinGet that could have exposed a moderator's GitHub token through a single pull request. The bug sat in an internal PowerShell triage tool that attached credentials to requests without checking the destination. An attacker could have pushed backdoored installers to roughly 14,000 packages under a trusted Microsoft badge. There is no evidence of exploitation in the wild.
read more β†’

Cloudflare Open-Sources Kitesurf Browser Engine

🟦 Cloudflare has open sourced Kitesurf, a stateless browser for AI agents that runs entirely on Workers. The project is available under the Apache 2.0 license on GitHub and includes an Engine, PageScript, and PageRenderer built with Rust and WebAssembly. Developers can build locally, connect via the Chrome DevTools Protocol (CDP) with tools like Puppeteer, and deploy to their own Workers accounts (paid plan required for Dynamic Workers). The team invites contributions and highlights ongoing efforts to improve compatibility, reliability, and efficiency.
read more β†’

Mass GitHub account hijack compromises CI secrets

πŸ”’ Aikido Security says an attacker used stolen credentials from 4,837 GitHub accounts to plant a secret-stealing payload into CI workflows, running in at least 1,806 repositories. SafeDep counted 8,093 repositories that received malicious commits; in many cases the stealer was added to existing workflows or delivered via npm postinstall hooks. The malware exfiltrates GitHub Actions secrets, cloud credentials, and repository data, often removing logs and reverting commits quickly. Owners must revoke tokens and keys, rotate secrets, enable 2FA, and inspect cloud trust policies and federated credentials for signs of compromise.
read more β†’

Claude Code setting files exposed thousands of secrets

πŸ”’ GitGuardian found that Anthropic’s Claude Code saves approved shell commands into a project-level .claude/settings.local.json, causing embedded API keys, database credentials, cloud tokens and passwords to be exposed across public GitHub repositories and Docker Hub images. The firm identified 31,088 distinct secrets across 23,276 repos, with 5,343 still valid at detection, and uncovered 613 secrets in public Docker images. The root cause is the β€œYes, and don’t ask again” approval storing full command strings; Docker’s COPY behavior and ignored .gitignore entries further propagated secrets into images.
read more β†’

Git fixes path-truncation flaw allowing code execution

πŸ”’ Git patched a critical vulnerability (CVE-2026-111760) that allowed malicious repositories with extremely long paths to bypass safety checks and write shortened names like .git, enabling attackers to replace submodule .git files with symlinks to malicious hooks or configuration. The fix, released in Git 2.56.1 and backported across 2.50–2.55 branches, rejects overly long paths before truncation. GitHub and other vendors are rolling out updates and advising users to install fixed versions and avoid recursively cloning untrusted repositories until patched.
read more β†’

GitHub launches npm package firewall in preview

πŸ›‘οΈ GitHub is previewing a package firewall that blocks suspicious npm packages at install time by inspecting metadata requests and package downloads. The feature, available to GitHub Enterprise Cloud customers, sits between endpoints or internal registries and upstream repositories and enforces policies like minimum package age, malware advisories, SLSA attestations, and install-script checks. Administrators configure controls and can approve exception requests for blocked packages.
read more β†’

Automated campaign exposes GitHub repo secrets via Actions

πŸ” An automated campaign named Gheist uses stolen GitHub tokens to create branches and plant workflows that print repository secrets into GitHub Actions logs, which attackers then download and delete. Wiz reports the campaign has affected private repositories and GitHub Enterprise environments since September 15, recovering over 13,500 planted branches across more than 850 compromised accounts. Public runs were paused by GitHub's suspicious-run safeguard, but private and Enterprise Server runs were not covered, leaving many secrets at risk.
read more β†’

OVHcloud CLI releases swapped via hijacked GitHub account

πŸ›‘οΈ An attacker hijacked a contributor's GitHub account and replaced download archives on five OVHcloud CLI releases on October 19, publishing malicious builds that could steal on-disk secrets. The swapped files were live for up to 94 minutes and affected installs or updates on specific macOS, Linux (x86_64 and arm64), and Windows x86_64 paths that did not verify hashes. OVHcloud removed the tampered archives, published an immutable v0.16.0 release, and advises rotation of any secrets that might have been exposed; a full postmortem is pending.
read more β†’

GhostAction attackers expand to phishing and stealers

πŸ”’ The GhostAction supply-chain actor evolved from injecting malicious GitHub Actions to phishing maintainers and delivering a credential stealer hidden in a fake font file. OpenSourceMalware reports the attacker registered my-github[.]com, used it for device-code OAuth phishing to harvest tokens, and added a second-stage VS Code launcher and stealer that persists on developer machines. Multiple repositories were compromised and data exfiltrated to attacker-controlled IPs.
read more β†’

GhostAction surge targets thousands of GitHub repos

πŸ›‘οΈ Since October 8–9, 2026, a renewed GhostAction campaign compromised roughly 1,900 GitHub accounts and targeted over 30,000 repositories, attempting to extract thousands of CI/CD secrets. Security firm GitGuardian observed the activity and noted evolving payloads that scan git history for AWS keys, tokens, and AI API keys. GitHub began blocking the malicious workflows on October 9, limiting later waves.
read more β†’

GitHub tightens npm trusted publishing expiry

πŸ”’ GitHub now expires newly created npm trusted publishing configurations after 48 hours if they don't complete an initial successful publish. The change validates and permanently binds the configuration only after that first publish and requires a new 48-hour window when repository or project identity changes. GitHub also blocks trusted tokens from issue_comment events and retains the existing pull_request_target restriction to reduce risks from reclaimed repository slugs.
read more β†’

SlugFest: npm Trusted Publishing validation flaw fixed

πŸ”’ Researchers at Boom Security disclosed a vulnerability in npm’s Trusted Publishing that allowed attackers to hijack packages by reclaiming abandoned GitHub repository names. The flaw stemmed from npm validating human-readable repo names instead of immutable numeric IDs, enabling adversaries to inherit publishing trust without stealing credentials. npm and GitHub have implemented mitigations, including a 48-hour expiry for unvalidated configurations and tighter token restrictions, while maintainers are urged to audit trust bindings.
read more β†’

Credential-stealing workflow campaign hits hundreds

πŸ”’ Cybersecurity researchers disclosed an active credential-theft campaign that used compromised maintainer GitHub accounts to inject malicious GitHub Actions workflows into more than 340 repositories. The malicious workflows, masquerading as Security Audit or GitHub Actions Security, exfiltrate repository secrets and credentials to a hard-coded IP address and scan the working tree and git history for API keys and tokens. The activity, attributed to the GhostAction campaign, has affected hundreds of users and led to thousands of secrets being harvested since late August 2026. Developers are urged to search for the offending workflow files, assume compromise, revoke affected credentials, and remove the injected workflows across branches and forks.
read more β†’

Over 543,000 Valid Credentials Exposed on GitHub

πŸ”’ Truffle Security scanned 224 million GitHub repositories and found 543,699 unique credentials that remained valid in July, appearing across more than 1.1 million files and forks. The median exposure time for a credential was 784 days, with about 10% older than 6.3 years and some dating back to 2009. GitHub's Push Protection reduced exposures in covered categories by 53%, but many secrets (like DB strings and Google API keys) remain outside its default scope. Researchers urge immediate rotation, history cleanup, and automated expiration of secrets.
read more β†’

Leaked GitHub App keys risk organization takeover

πŸ” GitGuardian discovered hundreds of publicly exposed GitHub App private keys that remain valid unless manually revoked. Their testing found many keys granted read or write access to private repositories and some allowed organization administration, enabling potential takeovers. The exposed keys included apps used by multiple organizations and internal one-off bots, increasing supply-chain risk. Experts recommend routine key rotation and prompt revocation to limit long-lived exposure.
read more β†’

Hundreds of GitHub App private keys still valid

πŸ”’ Research from GitGuardian found thousands of exposed GitHub App private keys in public code, with 474 still authenticating as 440 distinct Apps. The leaked keys never expire unless manually revoked, enabling holders to request indistinguishable access tokens and potentially gain wide repository and organizational privileges. Several high-impact keys affected private repositories and organization administration, prompting coordinated disclosures and key rotations.
read more β†’

Detecting and Quarantining Exposed AWS IAM Keys

πŸ”Ž This article examines how AWS mitigates publicly exposed IAM access keys through the AWSCompromisedKeyQuarantine managed policy, tracing its evolution across versions and explaining its role in responding to leaked credentials. It details the GitHub secret scanning partnership with AWS, a real-world timeline from a public exposure test, and practical monitoring strategies security teams can use to detect quarantine events in their logging environments. The piece also outlines Palo Alto Networks services that can assist organizations in assessment and incident response.
read more β†’

Attacker Hijacks AI Coding Assistant, Spreads Worm

πŸ›‘οΈ Mandiant reports an attacker hijacked an active AI coding-assistant session at an unnamed SaaS provider and used it to install an infostealer via a poisoned PyPI package. The attacker stole GitHub OAuth tokens and deployed the self-spreading Shai-Hulud worm across about 100 internal repositories, exfiltrating secrets and source code. Mandiant recommends verifying AI-recommended dependencies with checksums and allowlists, restricting extension access to secrets, and routing dependencies through controlled internal repositories to protect AI-assisted development.
read more β†’

GitHub outage confirmed β€” widespread service errors

⚠️ GitHub confirmed a widespread outage on August 17, 2026, reporting elevated error rates across the website, API, Actions, Pull Requests, and related services. The company observed ~20% error rates for web and API traffic, and roughly 50% errors for archive and raw repository downloads. Authentication services such as SAML and OIDC, plus SCIM and Team Sync, are affected, and GitHub Actions and Copilot reported degraded availability. The incident is under investigation and the root cause has not been disclosed.
read more β†’

Mozilla rotates GPG signing key after accidental exposure

πŸ” Mozilla updated the GPG subkey used to sign Firefox and Thunderbird artifacts after an unencrypted copy of the previous subkey was inadvertently committed to a private GitHub repository. The organization says the exposure risk is low because repository access was limited and its audit found no evidence of unauthorized access. Mozilla revoked the old key, published the new public key and revocation, and provided instructions for users who manually verify signatures or use RPM-based Linux distributions.
read more β†’