Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: credential-theft (40 articles)Clear

LiteLLM 1.107.0 compromised in supply chain attack delivering credential stealer and GitHub-controlled backdoor

Researchers at SafeDep, Socket, StepSecurity, and Upwind reported that LiteLLM version 1.107.0, a popular Python AI gateway, was published with malware through compromised GitHub CLI OAuth tokens belonging to three engineers. A cook.pth file runs a payload whenever the Python interpreter starts, even before LiteLLM is imported. The first stage, calling itself privcollect, harvests cloud tokens, developer credentials, private keys, AI tooling credential files, browser data, environment variables, and the proxy's saved keys and model config, exfiltrating over HTTP to litellm[.]dev/healthcheck. A second payload is a backdoor that fetches and runs further commands. The PyPI package and Docker images were pulled, and users should pin to 1.106.2.

Check
Check whether LiteLLM 1.107.0 was installed from PyPI or Docker, and if so revoke and replace all reachable credentials from a clean machine, then pin to 1.106.2.
Affected
Systems that installed LiteLLM 1.107.0 ran a credential stealer and backdoor on Python startup, exposing cloud tokens, keys, browser data, and the LiteLLM proxy's saved secrets.
Fix
Pin LiteLLM to 1.106.2 by digest, rotate every exposed credential, remove the cook.pth persistence, and block outbound traffic to the litellm.dev healthcheck exfiltration endpoint.

Attackers hijack over 300 Tor exit relays to intercept SSH sessions and steal passwords

A researcher found more than 300 malicious Tor exit relays, at their October 4 peak about 7.46 percent of exit capacity, rerouting SSH connections to twelve interception servers. The attackers edited relay torrc files to allow port 22, and each hijacked exit presented its own host key before connecting onward to the real server, so sessions worked while passwords typed by users who accepted the key were captured. Key-based logins could not be relayed. The operator of the largest affected relay family traced the root cause to the Ebury backdoor and a reused plaintext password with SSH password authentication left enabled. Tor flagged the relays by October 5.

Check
If you used SSH over Tor between October 1 and 5 and accepted a changed host key, treat typed passwords as stolen and rotate them immediately.
Affected
Users who sent SSH password logins through a hijacked Tor exit relay and accepted the interceptor's host key had their passwords and session activity captured.
Fix
Use key-based SSH rather than passwords, verify host keys, rotate any exposed credentials, and have relay operators check torrc files and hosts for the Ebury backdoor.

Credential-stealing GitHub Actions workflows planted across tens of thousands of repositories via compromised maintainer accounts

Socket, StepSecurity, and GitGuardian reported a resurgence of the GhostAction supply chain campaign, in which more than 500 GitHub accounts committed a credential-stealing workflow to tens of thousands of repositories since October 7. The attacker likely used maintainer personal access tokens leaked in infostealer logs, starting with the author of the pyxel game engine and spreading to other accounts. The injected workflow, disguised as a security audit, scans the working tree and full git history against 13 secret patterns, including AWS, Anthropic, OpenAI, and GitLab keys, and exfiltrates them over plain HTTP to a hardcoded address. Earlier GhostAction activity hit 772 repositories and thousands of secrets.

Check
Search repositories and forks for security-audit.yml or github_actions_security.yml workflows added since August 31, and if present assume compromise and rotate every exposed secret.
Affected
Repositories whose maintainer tokens were leaked had a rogue workflow injected that steals GitHub Actions secrets and any credentials in the working tree and git history.
Fix
Revoke compromised GitHub credentials, delete the malicious workflow from all branches and forks, rotate all exposed secrets, and store tokens outside infostealer-reachable locations.

Compromised Tensorlake npm package spreads Shai-Hulud worm that steals developer credentials and republishes itself

Socket and StepSecurity reported that version 0.5.144 of the tensorlake npm package, a TypeScript SDK, was published with obfuscated malware tied to the Shai-Hulud supply chain attack. A preinstall hook launches a loader that runs a worm under the Bun runtime. It harvests npm, GitHub, AWS, Vault, Kubernetes, and SSH credentials, .env files, cryptocurrency wallets, and configuration for Claude, Cursor, and other tools, then enumerates the victim's other packages and republishes them with forged provenance to spread. A PowerShell monitor watches the stolen GitHub token and runs a destructive handler if the victim revokes it, so remove the package before rotating that token.

Check
Check whether any project installed tensorlake 0.5.144, remove it before revoking tokens to avoid the destructive handler, then rotate all exposed credentials and audit republished packages.
Affected
Developers who installed the compromised tensorlake version had npm, GitHub, cloud, and SSH credentials stolen, and the worm may have republished their own packages with forged provenance.
Fix
Remove the malicious package, rotate npm, GitHub, cloud, and SSH credentials, review published packages and GitHub Actions workflows for tampering, and follow Socket and StepSecurity guidance on token revocation order.

ClickFix campaign smuggles payloads through browser cache to bypass Windows Run character limits

Microsoft Threat Intelligence detailed a ClickFix variant that pre-fetches malicious scripts into the browser cache, disguised as PNG files, so victims run content already stored locally rather than downloading a remote payload when they paste the attacker's command. The approach conceals the payload and sidesteps the roughly 260-character limit of the Windows Run dialog. The chain uses VBScript to enumerate browser cache files, pulls PowerShell from external servers, and injects .NET assemblies into legitimate processes such as timeout.exe to steal browser and device credentials before fetching further in-memory stages. The cache enumeration specifically references Firefox, and similar tricks have targeted macOS Terminal users.

Check
Train users against pasting commands from websites into the Run dialog or a terminal, and monitor endpoints for VBScript cache enumeration and injection into processes like timeout.exe.
Affected
Windows users tricked by a ClickFix lure run a payload pre-loaded into the browser cache, bypassing Run dialog limits to launch PowerShell and steal credentials.
Fix
Block the ClickFix workflow with user training, restrict Run dialog and script host usage, inspect browser cache abuse, and alert on .NET injection into benign binaries.

Official MCP Python SDK flaw lets malicious servers steal client OAuth credentials

The maintainers of the official Model Context Protocol Python SDK disclosed a flaw that lets a malicious MCP server trick an application built on the SDK into handing over the OAuth credentials it uses to log in to a real service. Affected versions sent the client secret, authorization code, and PKCE proof key to an attacker-controlled token endpoint, because the SDK did not always verify where the authorization server was. Cycode, which reported it, exchanged the stolen material for a valid access token carrying the app's permissions, and noted the long-lived client secret keeps working until rotated. Fixes are in versions 1.30.0 and 2.2.0.

Check
Upgrade the MCP Python SDK to 1.30.0 or 2.2.0, then rotate any OAuth client secrets that MCP clients may have sent to untrusted servers.
Affected
Applications built on affected MCP Python SDK versions can be induced by a malicious MCP server to leak their OAuth client secret, authorization code, and PKCE key.
Fix
Update the SDK, rotate exposed client secrets, and connect MCP clients only to servers whose authorization endpoints you trust and validate.

Bitget says attacker used third party security product flaw to steal 388 million dollars

Cryptocurrency exchange Bitget said the attacker who stole about 388 million dollars gained access through a vulnerability in a third-party security product the exchange used. The attacker exploited the flaw to obtain high-level internal credentials, then on September 24 used them to reach an internal management system and insert fraudulent withdrawal commands into wallet backend services, where they were treated as legitimate. The stolen funds came from Bitget's hot and warm wallets, while its offline cold wallets were unaffected. CEO Gracy Chen described the incident publicly, confirming the earlier statement that a critical wallet backend system had been compromised and used to spoof transaction data and trigger approvals.

Check
Review third-party security products in privileged positions for patch status and blast radius, and treat their credentials as high-value targets requiring isolation.
Affected
Organizations relying on a vulnerable third-party security product can have its high-level credentials stolen and abused to command core backend systems.
Fix
Inventory and patch third-party security tooling, scope its access tightly, add out-of-band approval for high-value transfers, and monitor for anomalous internal commands.

Compromised GitHub Actions came back online still executing Mini Shai-Hulud credential malware

Socket reported that two GitHub Actions, actions-cool/issues-helper and actions-cool/maintain-one-comment, were disabled a second time after their repositories became accessible again on September 16, months after being compromised in the May Mini Shai-Hulud campaign. When the repositories returned, their release tags were not cleaned up and still pointed to the malicious content introduced on May 18, so any workflow referencing either action by a version tag resumed downloading and executing the payload on its next run. The original May 18 compromise ran code that harvested credentials from CI/CD pipelines and exfiltrated them, activity linked to the Mini Shai-Hulud cluster through a shared exfiltration domain. GitHub has again disabled both repositories.

Check
Audit workflows for references to the two actions-cool actions, pin actions to trusted commit hashes, and rotate any CI/CD secrets exposed since September 16.
Affected
Pipelines referencing the affected actions-cool actions by version tag re-ran the May 18 payload after September 16, harvesting and exfiltrating CI/CD credentials.
Fix
Remove or repin the actions to vetted commits, rotate pipeline secrets, and prefer commit-hash pinning over mutable version tags for third-party actions.

Malicious npm package impersonates Twilio bug bounty probe to exfiltrate developer credentials

ReversingLabs detailed a malicious npm package, tw-pkgprobe-7731, that masquerades as an authorized Twilio bug-bounty research probe while harvesting developer data. Uploaded in mid-August by an account that no longer exists, it shipped eleven versions within about 45 minutes. Comments inside describe it as an authorized HackerOne probe that runs only inside Twilio's serverless sandbox and takes no destructive action. On execution it first checks for a Twilio developer environment and exits otherwise, then collects environment variables plus system details like mounts and temporary folders and exfiltrates them through a webhook. Later versions specifically target developers using Twilio APIs by searching for folders tied to particular Twilio account identifiers, sharpening the credential theft.

Check
Block and audit for tw-pkgprobe-7731 across developer and build environments, then rotate Twilio credentials and API keys exposed on any affected machine.
Affected
Developers integrating Twilio who installed the package inside a matching environment had environment variables and account-linked configuration harvested and sent to an attacker webhook.
Fix
Pin and vet npm dependencies, alert on packages that fingerprint the environment before acting, and restrict outbound webhooks from build and developer hosts.

Rogue external MFA provider in Entra captures user passwords during legitimate logins

Varonis Threat Labs detailed a post-compromise technique it calls TrustSink, in which an attacker holding a highly privileged Microsoft Entra account registers a rogue External Authentication Method as an external MFA provider. During normal sign-ins, Entra redirects users to the rogue provider to complete the second factor, and the attacker inserts a convincing Microsoft password prompt that captures the password in plaintext before returning a valid signed token, so the login completes with no error. In testing, every sign-in succeeded while the attacker server logged passwords with source IPs. Resetting a captured password does not remove the rogue provider, which persists in the configuration and works against any external provider model.

Check
Audit Entra External Authentication Methods for unrecognized providers, remove rogue entries, and tighten which roles can register or modify external MFA providers.
Affected
Tenants where an attacker already holds a highly privileged Entra role can have a rogue external MFA provider silently harvest every user's password during normal logins.
Fix
Restrict and monitor privileged Entra roles, alert on External Authentication Method changes, and review provider configuration after any privileged-account compromise.