Skip to content
HACKTECH

Cyber news digest

What broke, and what we check because of it.

Breaches, exploited vulnerabilities, supply chain compromises and new rules, written up for the people who buy security work, with what each one means for an organisation that runs the same kind of systems. Every item cites at least two sources and was verified against them before publication.

52 items214 cited sourcesLatest item 5 November 2026

Showing 5 items in Supply chain. Show all 52 items

October 2026

1 item

  • Supply chain

    GhostAction plants secret-stealing workflows in tens of thousands of GitHub repos

    GitGuardian reported on 7 October 2026 that between 31 August and 30 September a malicious workflow, github_actions_security.yml, was pushed to 772 public repositories belonging to 373 GitHub users and organisations, and its 13 October update said a second wave on 8 to 12 October targeted more than 30,000 repositories after the GitHub accounts of about 1,900 users were compromised. The Hacker News, citing OpenSourceMalware, reported a phishing kit on my-github[.]com, a domain resolving to the campaign's exfiltration IP, that sent a maintainer a fake GitHub security alert, captured the password and 2FA code through a reverse proxy and silently authorised an OAuth device flow with repo, workflow and read:org scopes. Six days after GitHub began blocking the workflow on 9 October, a second stage appeared that commits a VS Code task set to run when a folder is opened, and GitGuardian later counted 72,026 commits to 22,964 public repositories between 13 and 21 October.

    • Social engineering assessment
    • Secure development training
    • Incident response

August 2026

1 item

  • Supply chain

    ChainDrop worm spreads from hijacked keyv maintainer account to hundreds of npm packages

    On 4 August 2026 an attacker who had compromised the GitHub account of the keyv maintainer pushed malicious files to project main branches and cut releases, so poisoned versions of keyv, flat-cache, file-entry-cache, cache-manager and related packages were published to npm with valid provenance through the projects' own GitHub Actions workflows. The worm, which the community nicknamed ChainDrop and Datadog compares to Shai-Hulud, then used stolen npm tokens to republish other maintainers' packages. Published counts differ: Microsoft counted 'more than 400 packages across multiple unrelated publishers', Aikido's 5 August update said at least 444 packages across 1,381 versions, and BleepingComputer reported more than 1,300 packages and said the count was expected to grow. The install-time payload stole npm, GitHub, AWS, Kubernetes and HashiCorp Vault credentials.

    • Incident response
    • Application security audit
    • Cloud configuration review

May 2026

1 item

  • Supply chain

    Mini Shai-Hulud worm spans npm and PyPI; TanStack release pipeline abused

    Microsoft Security Research identified a resurgence of the Shai-Hulud worm family on 11 May 2026, reporting more than 170 npm packages and 2 PyPI packages across 404 malicious versions and describing it as the first supply chain attack to simultaneously span both registries in a single coordinated operation. In the TanStack wave, tracked as CVE-2026-45321, the attacker chained a pull_request_target workflow, GitHub Actions cache poisoning and extraction of an OIDC token from runner memory to publish 84 malicious versions across 42 @tanstack packages between 19:20 and 19:26 UTC, all with valid SLSA provenance, according to TanStack and Tenable. In a later wave reported on 20 May, a compromised @antv maintainer account spread the worm to downstream packages, and Microsoft said GitHub removed 640 malicious packages and invalidated 61,274 npm granular access tokens that had write permissions and 2FA bypass.

    • Application security audit
    • Incident response
    • Threat modelling

March 2026

2 items

  • Supply chain

    Hijacked axios maintainer account used to publish npm releases that installed a RAT

    On 31 March 2026 an attacker used the hijacked npm account of axios's lead maintainer to publish axios 1.14.1 and 0.30.4, which added a malicious dependency, plain-crypto-js@4.2.1, whose postinstall hook installed a cross-platform remote access trojan. The axios post-mortem says the attacker obtained the npm credentials through a targeted social engineering campaign and RAT malware on the lead maintainer's computer, and the maintainer said in the issue thread that 2FA was enabled on the account; the malicious versions were live for about three hours. Google Threat Intelligence Group attributed the activity to UNC1069, which it describes as a financially motivated North Korea-nexus actor, citing its WAVESHAPER.V2 backdoor and infrastructure overlaps.

    • Incident response
    • Social engineering assessment
    • Secure development training
  • Supply chain

    TeamPCP campaign hijacks Trivy Action tags, then backdoors LiteLLM and Telnyx on PyPI

    On 19 March 2026 an attacker using compromised credentials published a malicious Trivy v0.69.4 release, force-pushed 76 of 77 aquasecurity/trivy-action tags and replaced all seven setup-trivy tags with code that stole CI/CD secrets, according to Aqua's advisory and Datadog Security Labs. The Hacker News reported that the stealer identified itself as 'TeamPCP Cloud stealer', and Datadog linked later compromises of Checkmarx GitHub Actions on 23 March, LiteLLM 1.82.7 and 1.82.8 on 24 March and Telnyx 4.87.1 and 4.87.2 on 27 March to the same campaign. LiteLLM said it believes its compromise originated from the Trivy dependency used in its CI/CD security scanning workflow, and that initial evidence suggested the attacker bypassed its official CI/CD workflows and uploaded the malicious packages directly to PyPI.

    • Incident response
    • Cloud configuration review
    • Application security audit

Run the checks against your own systems

We pick the checks that apply to your systems. A 45-minute scoping call ends with a fixed quote and a proposed start date; the written scope follows by email.

Book the scoping callHow incident response works