posthog

ai and ML AI slop is good for business if you know what you're doingYour irresponsibility is someone else's opportunity SAAS Salesforce partners not seeing meaningful revenue from Agentforce AI platform, report saysShow us the money ai and ml AI companies are burning books, advocates complain to FTCFahrenheit 203, the temperature GPUs stop gorging on literature DEVOPS Go updates may delight diehard gophers but displease AI overlordsv 1.27 expands generics to support methods EDGE AND IOT Waymo has designed a robocar chip to stay ahead of Tesla5 nm ML accelerators promise 1,000+ TOPS, ultra-low latency Security Russians are posing as Signal support to launch phishing attacksPLUS: US takes down Iranian propaganda sites; Marketing company asks 'Why Do We Have Your Information?' And more! Security Microsoft patches failed to fix on-prem SharePoint, which is now under zero-day attackPLUS: China upgrades smartphone surveillance tools; Ring eases anti-snooping stance; and more Black Hat and DEF CON DEF CON Franklin project enlists hackers to harden critical infrastructureVoting village reports have been so successful, says Jeff Moss, that the whole of DEF CON will now be included Security EQT buys majority share in Swiss cybersecurity biz AcronisWent at equivalent of $3.5B+ valuation for entire firm, though portion sold not specified Malware Month Ten years since the first corp ransomware, Mikko Hyppönen sees no end in sightOn the plus side, infosec's a good bet for a long, stable career FOSS smashed one Microsoft monopoly. After 20 years of failure, it's time to smash anotherWord up GNOME can look like Windows – and Flashback can do it without extensionsNew 'Simple-taskbar' is an option, but there's a simpler, stabler way A moment of silence, please, for the final release of Debian on x86-32New Debian versions hit FOSSland in the form of 13.6 and 12.15 Baddies caught exploiting extensions bugs with perfect 10 scores on vulnerable Joomla websitesFlaws in iCagenda, Balbooa Forms extensions can impact open source CMS that powers a million sites worldwide Frame: A new X11 server – implemented directly in assemblyJoins yserver, Phoenix, and of course XLibre – and outlier Arcan Cinnamon 6.8 will support Wayland – if you want itNext version of Linux Mint’s desktop has both kinds of display server

The second wave of the Shai-Hulud supply chain attack has spilled over to the Maven ecosystem after compromising more than 830 packages in the npm registry. The Socket Research Team said it identified a Maven Central package named org.mvnpm:posthog-node:4.18.1 that embeds the same two components associated with Sha1-Hulud: the "setup_bun.js" loader and the main payload "bun_environment.js." The company told The Hacker News that org.mvnpm:posthog-node:4.18.1 was the only Java package identified so far. "This means the PostHog project has compromised releases in both the JavaScript/npm and Java/Maven ecosystems, driven by the same Shai Hulud v2 payload," the cybersecurity company said in a Tuesday update. It's worth noting that the Maven Central package is not published by PostHog itself. Rather, the "org.mvnpm" coordinates are generated via an automated mvnpm process that rebuilds npm packages as Maven artifacts. The Maven Central said they are working to implement extra protections to prevent already known compromised npm components from being rebundled. As of November 25, 2025, 22:44 UTC, all mirrored copies have been purged. The development comes as the "second coming" of the supply chain incident has targeted developers globally with an aim to steal sensitive data like API keys, cloud credentials, and npm and GitHub tokens, and facilitate deeper supply chain compromise in a worm-like fashion. The latest iteration has also evolved to be more stealthy, aggressive, scalable, and destructive. Besides borrowing the overall infection chain of the initial September variant, the attack allows threat actors to gain unauthorized access to npm maintainer accounts and publish trojanized versions of their packages. When unsuspecting developers download and run these libraries, the embedded malicious code backdoors their own machines and scans for secrets and exfiltrates them to GitHub repositories using the stolen tokens. The attack accomplishes this by injecting two rogue workflows, one of which registers the victim machine as a self-hosted runner and enables arbitrary command execution whenever a GitHub Discussion is opened. A second workflow is designed to systematically harvest all secrets. Over 28,000 repositories have been affected by the incident. "This version significantly enhances stealth by utilizing the Bun runtime to hide its core logic and increases its potential scale by raising the infection cap from 20 to 100 packages," Cycode's Ronen Slavin and Roni Kuznicki said. "It also uses a new evasion technique, exfiltrating stolen data to randomly named public GitHub repositories instead of a single, hard-coded one." The attacks illustrate how trivial it is for attackers to take advantage of trusted software distribution pathways to push malicious versions at scale and compromise thousands of downstream developers. What's more, the self-replication nature of the malware means a single infected account is enough to amplify the blast radius of the attack and turn it into a widespread outbreak in a short span of time. Further analysis by Aikido has uncovered that the threat actors exploited vulnerabilities, specifically focusing on CI misconfigurations in pull_request_target and workflow_run workflows, in existing GitHub Actions workflows to pull off the attack and compromise projects associated with AsyncAPI, PostHog, and Postman. The vulnerability "used the risky pull_request_target trigger in a way that allowed code supplied by any new pull request to be executed during the CI run," security researcher Ilyas Makari said. "A single misconfiguration can turn a repository into a patient zero for a fast-spreading attack, giving an adversary the ability to push malicious code through automated pipelines you rely on every day." It's assessed that the activity is the continuation of a broader set of attacks targeting the ecosystem that commenced with the August 2025 S1ngularity campaign impacting several Nx packages on npm. "As a new and significantly more aggressive wave of npm supply chain malware, Shai-Hulud 2 combines stealthy execution, credential breadth, and fallback destructive behavior, making it one of the most impactful supply chain attacks of the year," Nadav Sharkazy, a product manager at Apiiro, said in a statement. "This malware shows how a single compromise in a popular library can cascade into thousands of downstream applications by trojanizing legitimate packages during installation." Data compiled by GitGuardian, OX Security, and Wiz shows that the campaign has leaked hundreds of GitHub access tokens and credentials associated with Amazon Web Services (AWS), Google Cloud, and Microsoft Azure. More than 5,000 files were uploaded to GitHub with the exfiltrated secrets. GitGuardian's analysis of 4,645 GitHub repositories has identified 11,858 unique secrets, out of which 2,298 remained valid and publicly exposed as of November 24, 2025. Users are advised to rotate all tokens and keys, audit all dependencies, remove compromised versions, reinstall clean packages, and harden developer and CI/CD environments with least-privilege access, secret scanning, and automated policy enforcement. "Sha1-Hulud is another reminder that the modern software supply chain is still way too easy to break," Dan Lorenc, co-founder and CEO of Chainguard, said. "A single compromised maintainer and a malicious install script is all it takes to ripple through thousands of downstream projects in a matter of hours." "The techniques attackers are using are constantly evolving. Most of these attacks don't rely on zero-days. They exploit the gaps in how open source software is published, packaged, and pulled into production systems. The only real defense is changing the way software gets built and consumed."

Approximately 640 NPM packages have been infected with a new variant of the Shai-Hulud self-replicating worm in a fresh wave of attacks. The first Shai-Hulud iteration emerged in mid-September, when it infected over 180 packages in a supply chain attack leading to the exposure of GitHub, NPM, AWS, and Google Cloud credentials, Atlassian keys, and Datadog API keys. Upon execution on a victim’s system, the malware would search for NPM tokens, enumerate the packages the victim has access to, inject them with a post-install script to propagate itself, repackage them, and then publish the malicious package versions to the repository. Within days, the malware compromised dozens of developer accounts and published over 700 malicious package versions. It also harvested credentials and other secrets from the victim and published them to public repositories, and migrated private repositories to public ones. In the fresh version of the supply chain attack, launched over the weekend, the Shai-Hulud worm is even more aggressive and has been updated with destructive capabilities, security researchers warn. Unlike the previous version, the new Shai-Hulud samples rely on the NPM packages’ preinstall scripts for propagation, which “dramatically widens the blast radius across dev machines and CI/CD pipelines,” cybersecurity outfit Wiz warns. The worm drops two files, named ‘setup_bun.js’ and ‘bun_environment.js’, which contain a loader and the actual payload, respectively. According to Wiz, it also adds multiple GitHub Actions workflows, including a backdoor that supports command execution triggered via discussions in the GitHub repository. JFrog also observed that a system’s DNS would be hijacked following infection and that, if the worm does not find GitHub or NPM tokens to abuse, it executes a wiping function to delete all user data on Windows and erase all files and empty directories on Unix-based systems. The malware also launches privileged Docker containers and modifies sudoers files to gain root access for privilege escalation, Upwind notes. Wiz and Upwind said on Monday that they identified over 25,000 malicious repositories published by the malware. Wiz warned that it was seeing approximately 1,000 new packages being published every 30 minutes. The same as in September, Shai-Hulud seeks to harvest developer secrets, including tokens, cookies, and local workspace data, which it uploads to GitHub repositories under the attackers’ control. As ReversingLabs explains, the data exfiltration repositories associated with the attack have random names and the ‘Sha1-Hulud: Second Coming’ description. The company has identified 27,000 such repos. Unlike the previous version, the new Shai-Hulud iteration can infect up to 100 NPM packages maintained by any of its victims. The first trojanized package distributing the worm might have been @asyncapi/specs, which has roughly 1.4 million weekly downloads, ReversingLabs says. Aikido says it detected 36 packages from AsyncAPI that were trojanized, and that the attack later spread to PostHog packages, Postman packages, and many others. “Threat actors have slipped malicious code into hundreds of NPM packages — including major ones from Zapier, ENS, AsyncAPI, PostHog, Browserbase, and Postman. If a developer installs one of these bad packages, the malware quietly runs during installation, before anything even finishes installing,” Aikido warns. The compromised packages have a combined monthly download count of over 130 million. As Upwind points out, what makes the fresh supply chain attack a major threat is the speed and automation in turning each infected maintainer into a point of amplification. “Stolen tokens are reused instantly to republish malicious packages and inject rogue workflows, transforming Shai Hulud 2.0 into an ecosystem-wide worm rather than an isolated supply-chain incident,” Upwind notes. According to Sonatype principal security researcher Garrett Calpouzos, another worrying aspect of the attack is how the massive malicious source file that publishes harvested data to public repos confuses AI analysis tools. “It’s so large that it exceeds a normal context window and the models can’t keep track of everything they’re reading. I’ve asked both ChatGPT and Gemini to analyze it and I get different answers each time. Looking at their reasoning, they’re searching for obvious malware patterns — like calls to suspicious domains — and not finding any, so they incorrectly conclude it’s just a legitimate session or token management library,” Calpouzos said. Organizations are advised to scan their systems for indicators of compromise (IoCs), rotate potentially compromised secrets (including SSH keys, GitHub and cloud credentials, and tokens), and ensure strong multi-factor authentication is enforced. They should also review workflows and pipelines for anomalies, recreate self-hosted runners and CI agents from clean images, improve pipeline guardrails, and implement continuous monitoring to detect anomalous behavior. “To defend against this kind of attack, dev and security teams must treat npm package management and CI/CD pipelines as part of the threat surface. This means enforcing strict token/scoped access policies, limiting or auditing lifecycle scripts (especially preinstall/postinstall hooks), monitoring secrets in build environments and using behavioral analytics to detect unusual GitHub Actions workflows or outbound connections from build hosts. Given the worm‑like nature of Shai‑Hulud, time is of the essence: any delay in rotating tokens or cleaning compromised build agents can lead to rapid spread,” SOCRadar CISO Ensar Seker said. Related: Chinese Cyberspies Deploy ‘BadAudio’ Malware via Supply Chain Attacks Related: GlassWorm Malware Returns to Open VSX, Emerges on GitHub Related: Amazon Detects 150,000 NPM Packages in Worm-Powered Campaign Related: 136 NPM Packages Delivering Infostealers Downloaded 100,000 Times

Hundreds of trojanized versions of well-known packages such as Zapier, ENS Domains, PostHog, and Postman have been planted in the npm registry in a new Shai-Hulud supply-chain campaign. The malicious packages have been added to NPM (Node Package Manager) over the weekend to steal developer and continuous integration and continuous delivery (CI/CD) secrets. The data is automatically posted on GitHub in encoded form. At publishing time, GitHub returned 27,600 results corresponding to entries related to the recent attack. When the Shai-Hulud malware first appeared in the npm space in mid-September, and it compromised 187 packages with a self-propagating payload that used the TruffleHog tool to steal developer secrets. The threat actor automatically downloaded legitimate packages, modified the package.json file to inject a malicious script, and then published them on npm using compromised maintainer accounts. Charlie Eriksen, malware researcher at developer-focused security platform Aikido Security, discovered the new campaign earlier today, when there were 105 trojanized packages with Shai-Hulud indicators. Since then, the number grew to 492, counting only the package names. Later, the researcher warned that the secrets stolen in the supply-chain attack were leaked on GitHub. However, the campaign has grown exponentially to more than 27,000 malicious packages. Threat researchers at Wiz cloud security platform discovered around 350 unique maintainer accounts used in the campaign, noting that " 1,000 new repositories are being added consistently every 30 minutes in the last couple of hours." Eriksen clarified for BleepingComputer that the repositories on GitHub are indicative of compromised developers that used trojanized npm packages and thad GitHub credentials on their environment. A technical analysis of the new Shai-Hulud malware analysis from CI/CD security company Step Security explains that the new payloads are present in two files, one being setup_bun.js - a dropper disguised as a Bun installer. The second file is called bun_environment.js and is sizeable at 10MB. It relies on "extreme obfuscation techniques," Step Security says, such as a large hex-encoded string with thousands of entries, an anti-analysis loop, and an obfuscated function to retrieve every string in the code. Step Security describes five stages the malware executes during the attack, which include exfiltrating secrets (GitHub and npm tokens, secrets for cloud platforms like AWS, GCP and Azure) and a destructive step that overwrites the victim's entire home directory. Koi Security, a company providing protection solutions for self-provisioned software, tracks more than 800 npm packages compromised by Shai-Hulud, counting all infected versions of a package. The researchers confirmed the destructive step in the new Shai-Hulud variant, saying that the overwrite occurs only when a set of four conditions are met. Deleting a user's home folder happens if the malware cannot authenticate to GitHub, create a repository on the platform, fetch a GitHub token, or find an npm token. According to Wiz, the malicious code collects developer and CI/CD secrets and publishes them to GitHub repositories "with names referencing Shai-Hulud." The malicious code executes only during the pre-install stage and creates the following files: cloud.json contents.json environment.json truffleSecrets.json Stolen secrets are published on GitHub to automatically-generated repositories that have the description "Sha1-Hulud: The Second Coming." It appears that the threat actor has also gained access to GitHub accounts that they are now using to create repositories with the four files above. GitHub is deleting the attacker’s repositories as they emerge, but the threat actor appears to be creating new ones very fast. On the list of 186 packages that Aikido Security found to be compromised with a new version of the Shai Hulud malware, there are multiple packages from Zapier, ENS Domains, PostHog, and AsyncAPI. The compromised Zapier packages constitute the official toolkit for building Zapier integrations and are essential for Zapier developers. The EnsDomains packages are tools and libraries widely used by wallets, DApps, exchanges, and the ENS Manager app, to handle .eth names, resolving them to Ethereum addresses, linking IPFS content, validating names, and interacting with the official ENS smart contracts. All of the compromised packages are available for download from npm. However, in some cases, the platform displays a warning message about unauthorized publication of the latest version, indicating that the automated review has caught signs of a compromise. Developers are advised to check Aikido’s post for the complete list of the infected packages, downgrade to safe versions, and rotate their secrets and CI/CD tokens immediately. Wiz researchers recommend security teams to first identify the compromised packages and replace them with legitimate ones. They also urge organizations to rotate all credentials tied to npm, GitHub, and cloud providers. Aikido Security advises developers to disable npm postinstall scripts during continuous integration, if possible. The return of Shai Hulud comes at a time when GitHub introduced additional security measures to prevent supply-chain attacks on npm, following a series of high-impact attacks on the platform. However, the measures are being implemented gradually. BleepingComputer attempted to contact NPM about the campaign but our emails bounced as undeliverable. Update [November 24, 10:28 AM]: Article updated with information from Koi Security Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report