GitHub Confirms Internal Source Code Breach by TeamPCP Threat Actor A cybercriminal group known as TeamPCP has claimed responsibility for breaching GitHub’s internal systems, allegedly stealing proprietary data, including source code from approximately 4,000 private repositories. The threat actor announced the breach via a post on X (formerly Twitter), asserting access to sensitive internal assets tied to GitHub’s core platform. GitHub acknowledged the incident in a public statement, confirming unauthorized access to its internal repositories while emphasizing that customer data remains unaffected. The company is actively investigating the scope and impact of the breach. The incident highlights ongoing risks to software supply chains, as threat actors increasingly target development environments to exploit vulnerabilities or extract intellectual property. No further details on the attack vector or potential motives have been disclosed.

Trellix Confirms Source Code Repository Breach, Investigates Unauthorized Access Cybersecurity firm Trellix disclosed a security breach involving unauthorized access to a portion of its source code repositories. The company detected the compromise "recently" and has since engaged leading forensic experts to investigate the incident, while also notifying law enforcement. Trellix stated that its investigation has found no evidence that the accessed source code was exploited or that its release and distribution processes were impacted. However, the company did not specify the exact data accessed, the duration of the breach, or the threat actors responsible. Additional details will be shared as the investigation progresses. Formed in January 2022 through the merger of McAfee Enterprise and FireEye, Trellix is owned by Symphony Technology Group. The breach follows Google’s $5.4 billion acquisition of Mandiant, which was previously part of FireEye, around the same time. The incident remains under active investigation.

Bitwarden CLI Compromised in Supply Chain Attack Targeting npm On April 22, 2026, attackers briefly compromised the Bitwarden CLI by uploading a malicious version of the `@bitwarden/cli` npm package (version 2026.4.0). The package, available between 5:57 PM and 7:30 PM ET, contained a credential-stealing payload designed to spread to other projects. Bitwarden confirmed the incident, stating the breach was limited to its npm distribution channel and did not affect end-user vault data, production systems, or the legitimate CLI codebase. The company revoked compromised access, deprecated the malicious release, and initiated remediation. ### Attack Details Security firms Socket, JFrog, and OX Security reported that threat actors likely exploited a compromised GitHub Action in Bitwarden’s CI/CD pipeline to inject malicious code. The package included a preinstall script and a custom loader (`bw_setup.js`) that checked for the Bun runtime downloading it if absent before executing an obfuscated JavaScript file (`bw1.js`). The malware targeted: - npm and GitHub authentication tokens - SSH keys - Cloud credentials (AWS, Azure, Google Cloud) Stolen data was encrypted with AES-256-GCM and exfiltrated via public GitHub repositories under victims’ accounts, marked with the string "Shai-Hulud: The Third Coming" a reference to prior npm supply chain attacks. The malware also had self-propagating capabilities, using stolen credentials to inject malicious code into other packages. ### Connections to Other Attacks The attack shares infrastructure and malware overlaps with a recent Checkmarx supply chain breach, including: - The same telemetry endpoint (`audit.checkmarx[.]cx/v1/telemetry`) - Identical obfuscation routines (`__decodeScrambled` with seed `0x3039`) - Similar credential theft and GitHub-based exfiltration tactics Both campaigns have been attributed to TeamPCP, a threat actor previously linked to attacks on Trivy and LiteLLM. Bitwarden’s investigation found no evidence of broader compromise, but developers who installed the affected version were advised to rotate exposed credentials, particularly those tied to CI/CD pipelines and cloud environments.

Malicious Hackers Compromise Checkmarx KICS Tool to Steal Developer Secrets Hackers infiltrated the Checkmarx KICS (Keeping Infrastructure as Code Secure) tool, a popular open-source scanner for identifying vulnerabilities in code, dependencies, and configurations. The attack targeted Docker images, VS Code extensions, and Open VSX extensions, deploying malware designed to harvest sensitive data from developer environments. Security firm Socket uncovered the breach after Docker flagged malicious images in the official checkmarx/kics Docker Hub repository. The compromise extended to VS Code and Open VSX extensions, which secretly downloaded a hidden "MCP addon" from a hardcoded GitHub URL. This addon executed a multi-stage malware (mcpAddon.js) that stole credentials, including: - GitHub tokens - Cloud credentials (AWS, Azure, Google Cloud) - npm tokens - SSH keys - Claude configs - Environment variables The stolen data was encrypted and exfiltrated to audit.checkmarx[.]cx, a domain mimicking legitimate Checkmarx infrastructure. Attackers also automatically created public GitHub repositories for data exfiltration. The malicious Docker images were available for 83 minutes on April 22, 2026 (14:17:59–15:41:31 UTC) before being restored to legitimate versions. The fake v2.1.21 tag was removed entirely. While the TeamPCP hacking group, linked to previous supply-chain attacks (Trivy, LiteLLM), claimed responsibility, researchers found only pattern-based correlations and could not confirm attribution. Checkmarx confirmed the incident in a security bulletin, stating that all malicious artifacts were removed, exposed credentials were revoked, and an investigation with external experts is ongoing. The company advised users to block access to suspicious IPs (91.195.240.123, 94.154.172.43), revert to pinned SHAs, and rotate compromised secrets. Safe versions of affected tools include: - DockerHub KICS v2.1.20 - Checkmarx ast-github-action v2.3.36 - Checkmarx VS Code extensions v2.64.0 - Checkmarx Developer Assist extension v1.18.0

Vect Ransomware Turns Out to Be a Wiper, Destroying Victims’ Data Instead of Encrypting It A recent wave of supply-chain attacks targeting tools like Trivy and LiteLLM has left victims with little hope of data recovery, even after paying ransoms. According to Check Point Research, the Vect ransomware group partnering with TeamPCP isn’t actually encrypting files but instead permanently wiping any data larger than 128KB. Since January, Vect’s leak site has listed 25 organizations, with four added since March, when extortion efforts tied to the supply-chain attacks began. However, it remains unclear how many of these victims are linked to the Trivy and LiteLLM compromises. On April 15, Vect claimed two major targets Guesty (700GB) and S&P Global (250GB) allegedly tied to earlier TeamPCP breaches, though these claims lack independent verification. Neither company responded to inquiries. Vect and TeamPCP, which previously compromised security and developer tools like Checkmarx and Telnyx, announced their partnership on BreachForums, boasting of plans for larger supply-chain attacks and follow-on ransomware campaigns. Vect also integrated its ransomware-as-a-service (RaaS) with BreachForums, allowing registered users to access its malware, negotiation platform, and leak site. Check Point researchers gained access to Vect’s ransomware builder and discovered critical flaws. Instead of encrypting files, Vect 2.0 destroys any file exceeding 128KB by discarding essential decryption keys. The malware, available for Windows, Linux, and ESXi, uses libsodium-based encryption but fails to properly handle decryption nonces, making recovery impossible even for the attackers. Additional bugs and poor implementation further undermine its effectiveness, with researchers describing the code as "not technically sophisticated" and "amateur execution." The discovery confirms that victims of these attacks whether from supply-chain compromises or direct infections face irreversible data loss, regardless of ransom payments.

Former SSA Chief Data Officer Warns of Massive Social Security Data Breach A whistleblower has raised alarms over a potential national security disaster involving the exposure of sensitive Social Security data for every American with or who ever had a Social Security number (SSN). Chuck Borges, the former chief data officer of the Social Security Administration (SSA), resigned in August and filed a complaint alleging that employees of the Department of Government Efficiency (DOGE) uploaded a copy of the SSA’s database to an unsecured cloud environment. According to Borges, the breach if confirmed could leave personal data, including names, SSNs, and addresses, vulnerable to fraud and exploitation, with long-term consequences for millions of Americans. He has called for a congressional investigation into the alleged mismanagement, framing the incident as a severe threat to national security. The SSA has not publicly confirmed the breach, but the whistleblower’s claims highlight critical vulnerabilities in government data handling. If verified, the exposure could have far-reaching implications for identity theft, financial fraud, and cybersecurity risks across the U.S. The incident underscores ongoing concerns about federal agencies’ ability to safeguard sensitive citizen data.