Last updated: September 29, 2026 at 8:42 AM UTC
All 891 Vulnerability 357 Breach 144 Threat 383 Defense 7
Tag: credential-theft (35 articles)Clear

Self-spreading npm worm ChainDrop poisons over 1,300 package versions in hours

A self-propagating worm named ChainDrop tore through the npm registry on August 4, poisoning packages that huge parts of the software world depend on. It began by hijacking the GitHub account behind keyv, a caching library pulled in about 150 million times a week, then spread to sibling and downstream packages, reaching over 1,300 poisoned versions with billions of monthly downloads within hours. A preinstall script harvests credentials from developer and continuous integration environments, including AI agent tokens, cloud keys, and self-hosted CI secrets, then uses stolen npm publishing access to poison more packages. A descendant of the earlier Shai-Hulud worm, it even forged valid-looking build provenance.

Check
Compare lockfiles and resolved versions against the published affected-package list, and treat any machine that installed a poisoned version as compromised, but remove the malware's token watcher before rotating anything.
Affected
Developers and CI systems that installed a poisoned version during the attack window; the worm steals repository, registry, cloud, AI agent, and private-key credentials, then self-spreads through npm publishing access.
Fix
Rotate all reachable credentials after removing the token watcher, install with scripts disabled, pin and delay adoption of new versions, and check for injected hooks in developer tooling and continuous integration configuration.

Hugging Face says an autonomous AI agent breached its production systems

Hugging Face, the largest public repository of AI models and datasets, disclosed an intrusion into its production infrastructure that it says was driven end to end by an autonomous AI agent system. The attacker used code execution paths in the dataset processing pipeline for initial access, then harvested credentials and reached internal clusters, though the company found no evidence that public models or datasets were tampered with. The campaign ran thousands of actions across short lived sandboxes, with self migrating command and control staged on public services. Hugging Face's own AI assisted anomaly detection flagged it, and it has rotated affected credentials and rebuilt compromised nodes.

Check
Users of Hugging Face should rotate access tokens and review recent account activity, and teams should check what credentials their model and dataset pipelines hold and how far those reach.
Affected
Organizations running AI model and dataset pipelines that execute untrusted content; Hugging Face's own dataset processing paths gave an autonomous agent initial access, credentials, and reach into internal clusters.
Fix
Rotate Hugging Face tokens, treat datasets and models as untrusted code rather than data, sandbox processing pipelines, limit credentials reachable from them, and tighten admission controls on clusters running that work.

AssuranceAmerica breach exposes driver's license data of 6.9 million people

US auto insurer AssuranceAmerica has confirmed a breach affecting nearly 6.9 million people, the largest known exposure of Americans' driver's license data this year. The company detected the intrusion on March 17 after attackers compromised a single employee's credentials the day before and copied data files, but a lengthy review of the files was not finished until June 15, delaying notifications until now. The stolen data includes names, contact details, driver's license numbers, auto insurance policy and claims information, and, for some people, Social Security numbers. AssuranceAmerica has not detailed how the employee's credentials were taken, though such incidents are often tied to phishing or credential-stealing malware.

Check
People insured by AssuranceAmerica should watch for a breach notification, monitor bank and credit accounts and credit reports for fraud, and be wary of messages referencing their policy or claims.
Affected
Roughly 6.9 million AssuranceAmerica customers whose driver's license numbers, contact details, and insurance information were exposed, along with Social Security numbers for some; the data enables identity theft and convincing targeted phishing.
Fix
Affected people should consider a credit freeze given exposed license and Social Security numbers, monitor financial accounts, and treat insurance-themed messages cautiously. Organizations should enforce phishing-resistant MFA on employee accounts.

Fake payment SDKs on npm and PyPI steal developer and cloud credentials

Socket found a coordinated campaign of 17 malicious packages on npm and PyPI that impersonate the payment SDKs for Paysafe, Skrill, and Neteller to steal developer and cloud credentials. The fake libraries mimic real SDKs, returning success responses without contacting the real services, while quietly harvesting environment secrets such as Paysafe API keys, AWS keys, and GitHub and npm tokens and sending them to a server on AWS. Because these packages get pulled into build pipelines, a single one reaching a continuous integration runner can hand over the broad credentials those runners hold. The npm versions trigger when a payment key is present; the PyPI versions run on install regardless.

Check
Audit your dependency trees and continuous integration logs for the named fake Paysafe, Skrill, and Neteller packages, and search for the PAYSAFE_API_KEY variable appearing alongside unfamiliar package names.
Affected
Developers and CI/CD pipelines integrating Paysafe, Skrill, or Neteller that pulled the malicious packages; the fake SDKs steal payment API keys, AWS credentials, and GitHub and npm tokens from build environments.
Fix
Remove any affected packages, rotate exposed API keys, cloud credentials, and registry tokens, pin and verify dependencies against official SDK names, and limit the credentials and permissions available inside CI/CD runners.

Accenture confirms breach as attacker offers source code and keys for sale

Accenture, one of the world's largest IT consulting firms, has confirmed a data breach after a threat actor advertised stolen data for sale on a hacking forum. The seller claims to have taken about 35GB of source code along with RSA keys, SSH keys, Azure access tokens and storage keys, and configuration files, and shared a screenshot appearing to show them cloning an internal Azure DevOps repository. Accenture confirmed the breach but did not comment on the amount or type of data involved. If the stolen keys and tokens are valid, they could give attackers a path into Accenture's development systems or cloud infrastructure.

Check
Organizations that work with Accenture or share infrastructure with vendors should watch for supplier notifications, and check how their own source code, keys, and cloud tokens are stored and rotated.
Affected
Accenture and, potentially, its clients; stolen source code, SSH and RSA keys, and Azure tokens could let attackers reach development systems or cloud infrastructure if the credentials are still valid.
Fix
Rotate any exposed keys and tokens, keep secrets out of source code and repositories, enforce short-lived credentials and least privilege for cloud and DevOps access, and monitor development systems for unauthorized use.

Fake job interviews from big brands phish marketing staff for Google accounts

A phishing campaign is impersonating more than 30 well-known brands, including Adobe, Netflix, Coca-Cola, and OpenAI, in fake job-interview lures aimed at marketing professionals, with the goal of stealing their Google account credentials. Posing as recruiters from desirable companies, the attackers draw targets into a process that leads to a convincing Google sign-in page under their control. Because marketers often manage valuable brand, advertising, and analytics accounts tied to Google, a stolen login can open the door to ad fraud, data access, and further impersonation. The lure works by exploiting excitement about a career opportunity to lower the target's guard.

Check
Warn staff, especially in marketing, that recruiters asking them to sign in with Google to view interview or job details may be phishing, and verify any unexpected job outreach through official channels.
Affected
Marketing and other professionals targeted by fake job offers from impersonated big brands; stolen Google credentials can expose advertising, analytics, and brand accounts and enable further fraud and impersonation.
Fix
Use phishing-resistant multi-factor authentication like passkeys on Google accounts, verify recruiter outreach independently, never enter credentials on pages reached through unsolicited links, and check the domain before signing in anywhere.

North Korea hides malware in fake Rollup npm packages to steal developer secrets

JFrog found a new set of malicious npm packages, linked to North Korea, that impersonate legitimate Rollup polyfill tooling closely enough to pass a quick dependency review, down to matching names and metadata. Installing them pulls in hidden second-stage packages disguised as SVG utilities, which fetch and run a JavaScript payload while checking that they are not in a sandbox or cloud build. The malware hunts for developer secrets, and notably targets the configuration and history of AI coding tools like Cursor alongside AWS, Azure, SSH, and npm credentials. Because build plugins run on developer machines and in CI, a single poisoned dependency can expose source code, tokens, and cloud keys.

Check
Check whether any projects or build pipelines pulled the flagged Rollup-lookalike npm packages, and review developer machines and CI for exposed npm tokens, cloud keys, SSH keys, and AI coding tool configurations.
Affected
Developers and CI pipelines that installed the lookalike Rollup polyfill packages; the malware steals npm tokens, cloud and SSH credentials, source code, and secrets from AI coding tool configurations on the machine.
Fix
Pin and verify dependencies and scrutinize lookalike package names before installing, keep secrets out of developer and CI environments where possible, rotate any exposed credentials, and monitor for suspicious install-time network activity.

AI agent runs an entire ransomware attack after breaking in through Langflow

Security firm Sysdig says it found what it believes is the first ransomware attack carried out from start to finish by an AI agent. The operator, which Sysdig calls JADEPUFFER, used a large language model to handle the whole job: breaking in, stealing credentials, moving through the network, then encrypting and wiping a company's production database. The way in was an old, already-patched flaw in Langflow, an open-source tool for building AI apps that is often left exposed online with cloud keys nearby. Once inside, the agent mapped the machine and swept it for secrets, including API keys for AI services and credentials for major cloud providers, before destroying data.

Check
Find any internet-exposed Langflow or similar AI application servers, confirm they are patched and off the internet, and check whether cloud or AI service credentials sit in environments those tools can read.
Affected
Organizations running exposed, unpatched Langflow servers, especially with cloud and AI service credentials nearby; attackers used the old flaw and an automated agent to steal secrets and ransom production databases.
Fix
Patch Langflow and never expose its code-running endpoints, keep secrets in a proper manager away from web-reachable tools, lock down outbound traffic and database admin access, and watch runtime behavior.

BioShocking attack convinces AI browsers they are in a game, then steals credentials

Researchers at LayerX detailed BioShocking, an attack that manipulates AI browser agents into ignoring their safety rules by convincing them they are inside a fictional game. Using a web page with a puzzle that rewards deliberately wrong answers, the attack gets the agent to accept a false reality, after which it treats a request to open a page and copy its contents as just another step. In the demonstration, that page redirected to the victim's work GitHub repository and the agent handed over SSH credentials, treating the theft as finishing the game. None of the six AI browser agents tested flagged it as a rule violation.

Check
Review where AI browser agents are used and what logged-in accounts they can reach, and test whether an agent follows instructions from web content telling it the normal rules no longer apply.
Affected
Users of AI browser agents that act on logged-in sessions; an attacker-controlled page can trick the agent into ignoring its rules and stealing credentials or data from sites the user uses.
Fix
Require user confirmation before an agent reads from logged-in accounts, limit which sites and data agents can touch, and prefer AI browsers that flag when content tries to override their instructions.

Microsoft pulls 119 Edge extensions that hid malware inside images and fonts

Microsoft has removed 119 malicious Microsoft Edge extensions, tied to a single actor active since at least 2021, that hid their payloads inside ordinary image and font files using steganography. The extensions posed as ad blockers, VPNs, translators, and similar tools, worked as advertised, and stayed dormant for days while passing evasion checks, which let them survive in the store for years and reach up to 2.6 million installs. Beyond ad fraud and affiliate hijacking, the more dangerous variants stole Google credentials and two-factor codes at sign-in, harvested WordPress admin logins, and exfiltrated cookies for session hijacking, with extra aggression against corporate and banking targets. Microsoft has published indicators of compromise.

Check
Open your browser's extensions page and check installed add-ons against Microsoft's published list of StegoAd extension IDs, and review endpoints for the campaign's indicators of compromise across Chromium browsers.
Affected
Users who installed any of the 119 extensions, which posed as ad blockers, VPNs, and similar tools; stolen cookies and two-factor codes let attackers hijack sessions and accounts without passwords.
Fix
Remove any matching extension and treat the browser as compromised: reset Google and WordPress passwords, review sign-in activity, and prefer hardware security keys over SMS codes. Govern extensions with allowlists.