Tag: github
191 articles

GitHub AI Agents Exposed to Credential Theft via Prompt Injection
Security researchers have uncovered a shocking vulnerability in popular GitHub AI agents, demonstrating how a simple prompt injection technique can be exploited to steal sensitive credentials, leaving users alarmingly exposed. The findings highlight a disturbing lack of transparency from vendors, putting automation and service access at risk.

DPRK Hackers Exploit GitHub in Multi-Stage Attacks on South Korea
DPRK hackers have cleverly repurposed GitHub as a secret command center to launch multi-stage attacks on organizations in South Korea. This sneaky tactic starts with obfuscated Windows shortcut files, highlighting the growing creativity of North Korean threat actors.

GitHub Exposed to Infostealer Malware via Claude Code Leak
A recent leak of Claude's source code has taken a dark turn, with hackers exploiting the situation to spread Vidar, a notorious infostealer malware, by creating fake GitHub repositories that masquerade as legitimate projects. This cleverly crafted bait is luring unsuspecting users into a trap that can have serious cybercrime consequences.

GitHub Exploited in Sophisticated Malware Campaign
Malicious actors have launched a sophisticated malware campaign that exploits GitHub as a covert command-and-control channel, using trusted platforms to evade detection and wreak havoc on unsuspecting organizations. This multi-stage threat employs LNK files, embedded decoders, and PowerShell to establish persistence and exfiltrate sensitive data.

Secrets Sprawl Hits Alarming 34% Annual Surge
The alarming truth is that secrets sprawl has surged 34% in the past year, with a staggering 29 million new hardcoded secrets uncovered in 2025 alone. This explosive growth poses a daunting challenge for CISOs and the cybersecurity community, raising critical questions about our ability to safeguard sensitive information.

AI Companies: Stunning 65% Leak of Dangerous Secrets
A new study finds about 65% of leading AI companies have accidentally exposed sensitive secrets in public Git repositories like GitHub. Researchers warn those leaks — from API keys to model endpoints — could create stealthy “shadow access” and threaten roughly $400 billion in assets.

self-replicating worm: Shocking, Devastating NPM Breach
Imagine your everyday npm install quietly stealing your keys — researchers traced a self‑replicating worm to at least 187 NPM packages that exfiltrates developer credentials to GitHub each time an infected package is installed. This outbreak shows how fragile the software supply chain is and why immediate credential rotation, strict dependency hygiene, and better package vetting are essential.

delivery of pentest results: Must-Have Best Practices
Penetration testing uncovers real attack paths, but static PDFs and emails let critical fixes stall — automating delivery into ticketing, CI/CD, and dashboards turns findings into fast, measurable remediation. Adopt continuous workflows to shrink exposure windows, boost collaboration, and make pen-test insights actually stick.

Red Hat repositories Exclusive Critical Leak
Red Hat is scrambling after a hacking group called the Crimson Collective claims to have leaked roughly 570 GB from about 28,000 private repositories — including source code, internal notes and customer documents — a breach that could upend supply chains and privacy protections. If confirmed, assume exposure: rotate credentials, audit CI/CD and follow Red Hat’s guidance while investigators work to assess the full scope.

DDoS-as-a-Service: Risky ShadowV2 Exclusive Threat
Meet ShadowV2: a new campaign turning trusted developer platforms like GitHub Codespaces into a pay-as-you-go DDoS factory that lets attackers spin up ephemeral, high-bandwidth instances and sell DDoS-as-a-Service. The result is cheaper, harder-to-detect attacks and a wake-up call for platforms, security teams, and policymakers to rethink defenses before convenience becomes a weapon.

npm registry Must-Have Fixes Make It Safer
A recent wave of phishing and malware-laced npm packages has pushed GitHub to tighten registry security—introducing mandatory 2FA for popular maintainers, trusted publishing rules, and sweeping takedowns—to stop attackers from slipping malicious updates into countless JavaScript projects. These changes aim to make the ecosystem safer without losing the openness that powers modern development.

self-replicating worm: Stunning Risk to Dev Supply Chains
A self-replicating worm has infected nearly 200 NPM packages, stealing developer tokens and publishing them to public GitHub repos so each install can expose even more credentials. If you use open-source dependencies, now’s the time to audit builds, rotate keys, and lock down your developer workflows before the next propagation wave hits.

GitHub breach: Must-Have Fixes for Risky Attacks
When Salesloft’s GitHub repo was breached, attackers used exposed artifacts to access customer Salesforce data — and that compromise became the ground zero for a wider campaign affecting Drift. It’s a wake-up call to treat code repositories like sensitive infrastructure: rotate keys, enforce MFA, and scan for leaked secrets before attackers do.

Salesloft GitHub repository Massive Risky Breach
A March compromise of a Salesloft GitHub repo was used to pivot into Drift, touching hundreds of companies — including Google, Palo Alto Networks and Cloudflare — and exposing how fragile software supply chains and leaked tokens can be. Now’s the time to assume compromise: scan repos for secrets, rotate credentials, lock down permissions, and demand better transparency from your vendors.

crypto phishing Shocking Supply-Chain Nightmare
One phishing click that reset a maintainer’s 2FA let attackers slip backdoors into at least 18 popular npm packages — including debug and chalk — turning trusted libraries into supply-chain landmines. It’s a wake-up call: human error can ripple through the entire ecosystem, so stronger authentication, multi-person publishing, and tighter dependency hygiene can’t wait.

GPUGate malware: Exclusive Risky Search-Ad Campaign
Think twice before clicking that top search result—new GPUGate malvertising buys Google Ads and even fakes GitHub commit hashes to push trojanized installers that look legit. Protect yourself by sticking to official project pages, verifying signatures, and avoiding downloads from ad links.

GhostAction Shocking Breach: Devs’ Worst Nightmare
Imagine your CI tools quietly siphoning off keys — that’s GhostAction, a supply-chain campaign that weaponized GitHub Actions and packages to leak over 3,000 secrets across hundreds of repos. Take it as a wake-up call: rotate exposed credentials, pin and vet actions, and tighten workflow permissions before convenience turns into catastrophe.

malicious npm packages: Must-Stop Risky Supply-Chain Threat
Malicious npm packages and cloned GitHub repos are now weaponizing developer tooling to steal wallet keys and hijack Ethereum smart contracts, turning routine dependency installs into a direct route for theft. If you build dApps, treat every package as untrusted—use hardware wallets, isolate signing keys, and audit dependencies before they can cost you millions.

North Korean cyber-espionage: Exclusive Dangerous Campaign
Imagine getting a flawless meeting invite from a trusted colleague that’s actually a spy—researchers found a North Korean campaign using believable calendar invites and GitHub-hosted malware to target diplomats and foreign ministry staff. The attack’s clever blend of social engineering and mainstream developer tools shows how easily trust can be weaponized, risking sensitive negotiations and long-term access to government networks.

AI-generated code: Risky Threats & Must-Have Fixes
A new Checkmarx study reveals a surprising and worrying trend: AI-generated code now makes up over 60% of some codebases—and much of it contains known vulnerabilities—so the same tools that speed development can also widen your attack surface. Treat AI suggestions like draft work: add automated scans, clear guardrails, and reviewer sign-off to keep convenience from turning into a systemic security risk.

Big Tech Compliance: Stunning Failures Exposed
A cloud operator tied to crypto scams remains active across major platforms, revealing alarming gaps in how Big Tech enforces U.S. sanctions and putting users, payments, and national security at risk. We need clearer rules, better detection tools, and stronger public‑private coordination to stop bad actors from slipping through the cracks.

Web3 cyber threats: Critical Must-Have Defense Guide
EncryptHub is targeting Web3 developers with convincing fake AI platforms, so learn to spot spoofed sites, verify domains and social profiles, and never share private keys. Use hardware wallets, multisig, and secure development practices to keep your projects and funds safe.

npm package malware: Must-Have Best Defenses
Think a routine dependency update is harmless? The recent npm malware attack—where phishers stole maintainer tokens to publish malicious versions of five popular packages—proves supply-chain trust can be shattered and why maintainers, consumers, and registries must act now to enforce 2FA, rotate tokens, and verify publish provenance.

npm package security: Must-Have Guide to Risky Breaches
A targeted phishing attack that slipped malicious code into five npm packages shows how easily supply chains can be weaponized. Treat publish tokens like private keys—enable 2FA, rotate credentials, and demand package signing and provenance to stop the next breach.