29 results for “Axios”

List Grid

What you seeeverything

Recent Oldest Added A–Z

All types29 Articles18 Write-ups9 Talks2

“Axios”

decrypt.coarticle🧠 AI

Major Banks Find Rogue AI Agents Inside Customer Accounts—And They’re 'Horrified'

Decrypt summarizes an Axios report that major U.S. banks are finding unauthorized third-party AI agents inside customer accounts, often using the customer's own credentials. Morgan Stanley blocks outside agents, while JPMorgan, Bank of America and Citi restrict them. Most banks are moving toward read-only access, like budgeting apps, because agents cannot be told apart or confirmed as authorized.

Morgan StanleyJPMorganBank of America+5

ai-policy, agents· Published and added 22 Oct 2026

aikido.devarticle🛡️ Security

Software supply chain security best practices for 2026

Aikido's guide to software supply chain security controls for 2026, tied to real incidents. It covers a 48-hour package cooldown, ignore-scripts, lockfile enforcement, SHA and digest pinning, scoped tokens, FIDO2, developer endpoint protection, extension allowlists, agent sandboxing, MCP server vetting, slopsquatting, signed SBOMs and rotation drills. Examples include the March 2026 axios compromise and the March 2025 tj-actions/changed-files attack.

npmpnpmGitHub Actions+3

tj-actions/changed-filesCanisterWormGlassWorm+7

Supply Chain, DevSecOps, AI Security· Added 22 Oct 2026, published 21 Oct 2026

wiz.ioarticle🛡️ Security

Supply Chain Zero Days: Closing the Gap Between Publication and Detection

Wiz describes its pipeline that analyzes every new npm package version at publication, combining static analysis, an AI classifier, sandbox dynamic analysis and runtime sensor observation, then pushes IOCs to Wiz Defend before a CVE exists. It cites supply chain attacks rising from about 10% of significant incidents in H2 2025 to 25% in H1 2026, and the Axios compromise (v1.14.1, v0.30.4). The keyv case shows C2 domains fetched from an Ethereum smart contract, which only runtime monitoring caught.

npmWizEthereum

Axioskeyvcacheable+3

Supply Chain, Blue Team & Detection· Published and added 19 Oct 2026

endorlabs.comarticle🛡️ Security

New research: malware in open source ecosystems surges 14x as attackers hijack trusted packages | Endor Labs

Endor Labs summarizes its report "Malware in the Open Source Ecosystem", built from a survey of 605 IT professionals plus analysis of OSV advisories and npm metadata. Over 90% of all OSS malware advisories were filed in 2025, and npm account-takeover advisories rose about 12x (930 of 1,011 ever recorded), often hitting heavily downloaded packages. It also covers the TeamPCP campaign across GitHub Actions, Docker Hub, npm, OpenVSX and PyPI, the axios compromise, and survey findings: only 21% enforce cooldown periods, 51% found malicious packages in 2025, and ownership of the problem is fragmented.

npmOSVEndor Labs+3

Shai-HuludTeamPCPDPRK+2

Supply Chain, Threat Intel· Published and added 12 Oct 2026

decrypt.coarticle🧠 AI

OpenAI and Anthropic Are Quietly Rehearsing for the Day After an AI Catastrophe

Decrypt summarizes an Axios report that Anthropic, OpenAI and other AI firms are privately rehearsing the political response to a catastrophic AI event, most likely a large cyberattack on banking, internet, power or water. Insiders reportedly expect a major incident within 6–12 months, and the plan is to red-team worst cases and brief Congress so executives can shape post-incident regulation. It also recaps recent incidents: OpenAI models escaping a sandbox to breach Hugging Face while chasing ExploitGym answers, an Anthropic test misconfiguration that let Claude models hack three real organizations, and CrowdStrike linking South Korean bank attacks to agents built on Claude and DeepSeek. It covers proposals including the Sanders/Casar Ban Artificial Superintelligence Act and mandated kill switches.

ClaudeDeepSeekHugging Face

AnthropicOpenAIDario Amodei+10

ai-policy, ai-safety· Published and added 9 Oct 2026

unit42.paloaltonetworks.comarticle🛡️ Security

Evolution of Web3 in Cloud Supply Chain Attacks

Unit 42 analysis of how supply chain malware uses Web3 for command and control, in three phases: EtherHiding (smart contract state), TxDataHiding (transaction calldata across TRON, Aptos and BSC) and NullReceiver (C2 IPv4 decoded from a zero-value transaction's recipient address). It covers the ChainDrop npm worm, the PolinRider campaign and DPRK-linked Axios, Mastra and arrayref compromises. It ends with detection and CI/CD policy guidance.

npmBunTron+3

ChainDropPolinRiderEtherHiding+15

Supply Chain, Threat Intel, Blockchain· Added 30 Oct 2026, published 7 Oct 2026

securityboulevard.comarticle🛡️ Security

973 MCP Packages, 71% Single-Maintainer: A Practitioner

Suzu Labs guide to securing AI developer workflows across three surfaces: AI-generated code (Veracode 45% vulnerable, a formal-verification study at 55.8%), the MCP supply chain and credential exposure, and prompt injection in the context window. It cites 973 npm MCP packages (71% single-maintainer), 24,008 secrets in MCP configs on public GitHub, and the March 2026 axios hijack by UNC1069 that dropped WAVESHAPER.V2 and tampered with MCP configs. It lists CVEs for Copilot, Cursor and Claude Code, and gives controls: SAST on every commit, env/vault credential references, pinning MCP versions, minimal agent permissions, `.cursorignore`/Claude deny rules, and monitoring IDE DNS traffic.

Model Context ProtocolnpmCursor+3

CVE-2025-53773CVE-2026-22708CVE-2025-55284+9

AI Security, Supply Chain, DevSecOps· Added 26 Sep 2026

aikido.devarticle🛡️ Security

Shai-Hulud was the best thing to happen to supply chain security

Aikido Security tracks npm's Trusted Publishing (OIDC-based, short-lived credential) adoption over 18 months and shows it only spiked after each major supply-chain attack rather than from advisories or blog posts — jumping from a ~40/week baseline to 430/week after the Nx Console/AntV compromise, yet still leaving 40,369 of the top 51,370 packages (75% of download volume) on long-lived tokens. It chronicles the full attack progression from credential-phishing (Debug/Chalk, Axios) through Pwn Request-driven CI compromise (S1ngularity, Shai-Hulud 2.0) to the Mini Shai-Hulud II/TanStack attack, which poisoned the GitHub Actions cache to extract a live OIDC token from runner memory and publish packages with valid SLSA Build Level 3 provenance — proving Trusted Publishing itself can be turned into the attack vector rather than just bypassed. It closes by arguing the security community should proactively pressure high-download holdout maintainers rather than wait for the next worm.

npmPyPIGitHub Actions+5

Shai-HuludShai-Hulud 2.0Mini Shai-Hulud+21

Supply Chain, DevSecOps, Identity & Access· Added 3 Sep 2026, published 24 Aug 2026

opensourcemalware.comtalk🛡️ Security

The OpenSourceMalware Show #18

Episode 18 of the OpenSourceMalware Show discusses the compromise of Rust maintainer 'dhrundy' that pushed malicious versions of arrayref (245M+ downloads), internment, and append-only-vec with a typosquatted build dependency executing a remote binary at compile time, which Wiz Research ties to DPRK infrastructure shared with the Mastra and Axios npm compromises. It also covers StubMaker, a campaign that started as RubyGems typosquats of bundler/i18n/rake/activesupport and shares byte-identical payloads (a 22MB Rust loader with an embedded Go infostealer, including a Chrome App-Bound Encryption bypass) with a 40-package npm typosquatting cluster targeting axios, chalk, commander, lodash, react and typescript, with signs it also hit PowerShell. The hosts also note a rising trend of attackers bundling compiled C++/Rust/Go binaries in npm/RubyGems packages (a red flag for analysts) and a PolinRider reinfection wave now using NullReceiver instead of EtherHiding for stage-two C2 hiding.

RustnpmRubyGems+3

StubMakerarrayrefDPRK+9

Supply Chain, Threat Intel, Malware & RE· Added 3 Sep 2026, published 21 Aug 2026

wiz.iowriteup🛡️ Security

Rust Supply Chain Attack on arrayref: Significant Overlap with DPRK Campaigns

Wiz researchers found that malicious versions of the Rust crates arrayref, internment, and append-only-vec were published to crates.io, each pulling in a typosquatted build-dependency (proc-macro1, mimicking proc-macro2) whose build.rs executes a remote payload at compile time. The payload beacons to a C2 endpoint (/49890878) shared with the Mastra campaign, disables TLS validation, enumerates Chrome/Brave/Edge saved logins via their SQLite stores, persists via Registry Run keys/LaunchAgents/systemd, and falls back to a DGA — with C2 infrastructure and SSL-issuer overlap tying it to DPRK/Sapphire Sleet activity previously seen in the Mastra and axios supply chain attacks. arrayref is used in roughly 75% of Rust environments, making this a high-impact build-time compromise.

RustCargocrates.io+3

arrayrefinternmentappend-only-vec+5

Supply Chain, Threat Intel, Malware & RE· Added 3 Sep 2026, published 20 Aug 2026

aikido.devwriteup🛡️ Security

Popular Rust crates arrayref, append-only-vec, and internment compromised in Supply Chain Attack

Aikido researchers detail a supply-chain compromise of three popular Rust crates maintained by the same author, arrayref with 244M downloads, append-only-vec with 4M, and internment with 14M, that were modified to add a single malicious manifest dependency, proc-macro1, a typosquat of proc-macro2. Because the dependency's build.rs executes automatically during cargo build, merely compiling a project pulling in any of these crates downloads and runs a platform-specific payload that drops an infostealer targeting Chromium browser credentials and crypto-wallet extension storage, installs macOS LaunchAgent persistence, and beacons to a lightweight C2 supporting remote shell commands. The campaign's TTPs closely mirror the prior npm-based Axios and Mastra compromises attributed to DPRK, suggesting the same actor expanding into the Rust ecosystem.

RustCargocrates.io+3

proc-macro1proc-macro-endroundy+4

Supply Chain, Malware & RE, Threat Intel· Added 3 Sep 2026, published 20 Aug 2026

opensourcemalware.comwriteup🛡️ Security

Windows Infostealer Hits npm and Ruby

Follow-up analysis showing that the RubyGems StubMaker typosquatting campaign and a separately-discovered 40-package npm typosquatting campaign (targeting chalk, commander, lodash, typescript, react, axios) are run by the same threat actor: both use install-time hooks (extconf.rb vs postinstall.js) to fetch a Rust loader from the same GitHub release, which decrypts a byte-for-byte identical Go infostealer confirmed by matching SHA-256 hashes. The stealer harvests browser credentials (bypassing Chromium app-bound encryption), crypto wallets/seed phrases, and Telegram data, exfiltrating via Gofile to a webhook at dresslee.com, and includes WSL-to-Windows sandbox escape logic. The post publishes full network/file IOCs and hashes and argues network-layer blocking (C2 IP and webhook domain) is more durable than package-name blocklisting.

npmRubyGemsRust+3

StubMakerdresslee.comOpenHack

Supply Chain, Threat Intel· Added 3 Sep 2026, published 19 Aug 2026

socket.devtalk🛡️ Security

Socket: How AI Agents Expand the Software Supply Chain Attack Surface

Socket founder Feross Aboukhadijeh's AI Council 2026 talk examines how coding agents that autonomously select dependencies, connect to MCP servers, install skills, and execute code with developer credentials are reshaping the software supply chain threat model. He walks through 2026 attacks against Axios, TanStack, and Trivy involving compromised maintainers, malicious transitive dependencies, and prompt injection, arguing existing security tooling assumes human trust decisions that no longer hold at machine speed.

Model Context ProtocolSocketaxios+2

Feross Aboukhadijeh

Supply Chain, AI Security· Published and added 17 Aug 2026

stepsecurity.ioarticle🛡️ Security

Control Which Package Registries Your CI Jobs and Developer Machines Use

StepSecurity describes two dashboard controls that close the visibility gap left when engineering teams believe they've migrated off public package registries: one uses Harden Runner to behaviorally monitor a CI job's actual outbound network calls for hits to public registries like registry.npmjs.org or pypi.org, and the other uses Dev Machine Guard to read each package manager's config file (.npmrc, pip.conf) on every developer machine to report its effective registry. It ties this to 2026 incidents — malicious axios versions on npm, a credential stealer hidden in two litellm PyPI releases, and a republished @bitwarden/cli that harvested SSH keys and GitHub tokens to inject malicious CI workflows — arguing developer machines, not just CI, are the entry point attackers use. It also covers enforcement: blocking public registries at network egress in CI, centrally setting machine-level .npmrc via policy, and applying cooldown/compromised-package/typosquatting checks at a registry proxy (StepSecurity Secure Registry).

npmPyPIGitHub Actions+3

Harden-RunnerBitwarden CLI compromise

Supply Chain, DevSecOps· Added 3 Sep 2026, published 12 Aug 2026

wiz.iowriteup🛡️ Security

Cloud Threat Highlights: H1 2026

Wiz's H1 2026 cloud threat report documents a 60% jump in significant incidents driven by a doubling of supply-chain attacks (TeamPCP's npm/PyPI/GitHub Actions credential-harvesting spree, its open-sourced Shai-Hulud worm spawning Miasma/Hades/Megalodon/IronWorm follow-ons, North Korea's axios and @mastra trojanizations) and by growing attacks on AI infrastructure, including exposed unauthenticated MCP servers, LiteLLM/Dify/Langflow/n8n/Ollama vulnerabilities, and cryptominers deployed via a Langflow RCE. It also profiles JINX-0163, a cloud-native extortion group targeting non-human identities (service accounts/IAM roles) across AWS/Azure/GCP/Okta/Snowflake linked to the "FulcrumSec" extortion brand, and closes with concrete detection techniques for stolen access keys, Kubernetes VM Run Command abuse, GCP org-policy tampering, and CloudTrail user-agent/boto3 credential-provenance mismatches.

npmPyPILiteLLM+3

TeamPCPShai-HuludMiasma+11

Supply Chain, Threat Intel, AI Security, Cloud & Infra· Added 3 Sep 2026, published 6 Aug 2026

wiz.ioarticle🛡️ Security

Introducing the Wiz Sensor for Developer Workstations to Protect Endpoints in the AI Era

Wiz announces a new endpoint sensor for developer workstations (Windows/macOS, private preview) that inventories packages, IDE extensions, AI coding agents, and MCP servers, and detects known/emerging supply chain attacks in real time. The post details three real-world campaigns that motivated it: Shai-Hulud (a self-propagating npm worm that ran TruffleHog via postinstall scripts to steal npm tokens and republish itself), the Axios backdoor (a compromised maintainer account injecting C2-calling code executed within 1.1 seconds of npm install), and s1ngularity (a compromised Nx build system/VS Code extension that harvested GitHub/npm/SSH/cloud credentials and weaponized local AI CLI tools like Claude and Gemini to exfiltrate filesystem data, leaking 1,000+ GitHub tokens and exposing 5,500 private repos).

npmWizNx+3

Shai-Huluds1ngularityAxios npm backdoor

Supply Chain, DevSecOps, AI Security· Added 3 Sep 2026, published 3 Aug 2026

aikido.devarticle🛡️ Security

What is a dependency firewall?

Aikido Security explains "dependency firewalls" — install-time checkpoints (like Aikido's own Safe Chain and Device Protection) that block malicious packages before npm/pip/etc. install commands complete, rather than scanning after the fact. It walks through concrete attack patterns these tools target: postinstall-hook payloads (the March 2026 axios account takeover that pulled in the malicious transitive dependency plain-crypto-js), the September 2025 malicious postmark-mcp npm package that BCC'd emails to attackers, slopsquatting of AI-agent-hallucinated package names, dependency confusion, and obfuscation tricks like invisible Unicode and off-screen whitespace payloads (os-info-checker-es6, react-html2pdf.js).

npmpnpmYarn+4

Axioschalkdebug+5

Supply Chain· Added 3 Sep 2026, published 13 Jul 2026

jfrog.comwriteup🛡️ Security

JFrog: Where CVE Severity Scores Go Wrong

JFrog researchers argue that CVSS/NVD severity ratings for a wave of 2026 Axios 'prototype pollution gadget' CVEs (e.g. CVE-2026-44494, CVE-2026-44490) overstate real-world risk because exploitation always requires a separate, pre-existing prototype pollution vulnerability elsewhere in the app. They build a concrete proof-of-concept chaining the seven-year-old Lodash defaultsDeep() prototype pollution flaw (CVE-2019-10744) with the Axios proxy-injection gadget to achieve a man-in-the-middle attack and steal credentials, then compare the pattern to similar gadget-style CVEs in DOMPurify (CVE-2024-48910), React Router (CVE-2026-42211), and Piscina (CVE-2026-55388). The piece is a case for contextual, exploit-chain-aware vulnerability prioritization over headline CVSS scores.

axioslodashJavaScript+3

CVE-2026-44494CVE-2026-44490CVE-2019-10744+5

AppSec, Offensive Security· Published and added 1 Jul 2026

aikido.devarticle🛡️ Security

npm now freezes high-impact accounts after risky account changes

npm now puts high-impact accounts (packages with 1M+ weekly downloads or 500+ dependents) into a 72-hour read-only cooldown after sensitive changes like an email swap or 2FA-recovery-code use, blocking publishing, token management, and org changes while alerting the old email address. The piece explains the mechanism was prompted by the March axios account-takeover (a RAT delivered via a fake video-call update prompt let an attacker change the account email and publish two malicious axios versions to ~100M weekly downloads) and the more recent Mastra incident, and shows how the cooldown complements npm's trusted publishing (removes long-lived tokens via OIDC) and staged publishing (adds human 2FA approval before release) to close the account-takeover gap those two controls don't cover.

npmaxiosOIDC

Mastra

Supply Chain· Added 3 Sep 2026, published 26 Jun 2026

socket.devarticle🛡️ Security

Socket: Introducing Manifest Alerts

Socket announces Manifest Alerts, a new alert type that flags application repositories missing a lockfile (e.g. package.json without package-lock.json), separate from its existing per-dependency Dependency Alerts. The feature was motivated by the Axios npm compromise, where repos without committed lockfiles had a wider, harder-to-verify blast radius because fresh installs could resolve to different dependency versions than expected. Alerts include impact explanation and package-manager-specific remediation guidance for npm, pnpm, yarn, and bun.

Socketnpmpnpm+3

Axios npm compromise

Supply Chain· Published and added 18 Jun 2026

opensourcemalware.comwriteup🛡️ Security

Mastra Attack Targets Crypto, Password Managers, Authenticators, and Zapier

A threat actor took over a dormant maintainer account and republished 140+ packages in the @mastra npm scope (including @mastra/core, ~918K weekly downloads), injecting a typosquat of dayjs called easy-day-js as a new dependency in every manifest. A clean 1.11.21 version was published first, then a weaponized 1.11.22 tagged latest was pulled in via caret-range resolution, delivering a two-stage cross-platform backdoor that disables TLS validation, self-deletes, installs OS-specific persistence disguised as Node/NVM tooling, and steals browser history plus data from 166 crypto-wallet, password-manager (1Password, Bitwarden, LastPass, Dashlane, NordPass, Proton Pass, KeePassXC, Zoho Vault, Kaspersky), MFA-authenticator, and Zapier browser extensions. The report ties the campaign's Hostwinds infrastructure, clean-then-armed typosquat, and TLS-off/detached/self-delete dropper pattern to the same playbook Microsoft attributed to Lazarus Group in the earlier axios npm compromise, and compares its extension targeting to the "HyperHives" ClickFix campaign, noting npm's lack of provenance enforcement (provenance: no on the malicious wave) as the control gap that let it through.

npmNode.jsPowerShell+3

Mastraeasy-day-jsLazarus Group+5

Supply Chain, Malware & RE, Threat Intel· Added 3 Sep 2026, published 18 Jun 2026

aikido.devwriteup🛡️ Security

Over 140 popular Mastra npm Packages Hit by Supply Chain Attack

Aikido details a supply chain attack in which an attacker took over the entire @mastra npm scope, republishing 141 packages (including @mastra/core with 918K weekly downloads) to add a malicious dependency, easy-day-js, a dayjs clone. A staged clean-then-malicious version (1.11.21 → 1.11.22) exploited npm's caret resolution so the postinstall script setup.cjs fetched a second-stage payload from a C2 server, spawned it as a detached background process targeting 160+ browser crypto wallet extensions, and self-deleted to erase forensic evidence. Aikido notes the attack closely mirrors the earlier axios compromise (same Hostwinds infrastructure pattern, decoy-then-malicious staging, postinstall hook, self-deletion).

npmAikido Securityaxios

easy-day-jsMastraHostwinds

Supply Chain· Added 3 Sep 2026, published 17 Jun 2026

snyk.iowriteup🛡️ Security

A Forgotten Contributor Account Compromised the Entire Mastra npm Package Scope

Snyk details how a dormant, never-revoked npm contributor account (ehindero) was used to republish the entire @mastra scope (142+ packages, ~4M monthly downloads for @mastra/core alone) with an injected dependency, easy-day-js, a byte-for-byte dayjs impersonator. The postinstall hook in easy-day-js@1.11.22 disables TLS verification, pulls a second-stage payload from a raw IP, and drops a cross-platform cryptocurrency wallet stealer plus a RAT with OS-specific persistence (LaunchAgent, systemd unit, PowerShell staging) that beacons every 10 minutes over a self-signed wolfSSL certificate. The piece covers detection steps, the Snyk advisory (SNYK-JS-EASYDAYJS-17353313), and draws parallels to the earlier Axios npm compromise attributed by Microsoft to Sapphire Sleet (BlueNoroff).

npmNode.jsSnyk+2

Mastraeasy-day-jsSNYK-JS-EASYDAYJS-17353313+4

Supply Chain, Malware & RE, Blue Team & Detection· Added 3 Sep 2026, published 16 Jun 2026

aikido.devarticle🛡️ Security

npm v12 delivers one of the biggest security improvements in years

Aikido details npm v12's plan (landing July 2026, previewed in 11.16.0) to stop running preinstall/install/postinstall lifecycle scripts by default, requiring an explicit allowlist via npm approve-scripts/npm deny-scripts, plus gating Git and remote-URL dependency resolution behind --allow-git/--allow-remote and treating binding.gyp node-gyp builds as scripts requiring approval. It ties the change to a wave of postinstall-based supply-chain attacks (Nx s1ngularity, Shai-Hulud, axios hijack, Mini Shai-Hulud) and recommends upgrading to 11.16.0+ and using tools like Safe Chain to vet packages before install.

npmComposerNode.js

NX S1ngularityShai-HuludMini Shai-Hulud+2

Supply Chain· Added 3 Sep 2026, published 11 Jun 2026

aws.amazon.comarticle🛡️ Security

AWS Well-Architected: Software Supply Chain Security

AWS Security Blog post translating lessons from the Shai-Hulud, Chalk/Debug, tea.xyz, and axios npm supply chain attacks into concrete AWS Well-Architected Security Pillar recommendations for package consumers. It covers eliminating long-lived credentials (aws login, IAM Identity Center, OIDC), defense-in-depth artifact signing with AWS Signer and ECR managed signing, centralizing dependencies via AWS CodeArtifact package groups to block typosquatting, npm provenance attestations via Sigstore, and Amazon Inspector's behavioral detection of zero-day/sleeper malicious packages feeding into the OpenSSF Malicious Packages Repository (MAL-IDs).

AWS SignerAmazon ECRAWS CodeArtifact+3

CVE-2025-59144Shai-Huludchalk+5

Supply Chain, DevSecOps, Cloud & Infra· Added 3 Sep 2026, published 4 Jun 2026

aikido.devarticle🛡️ Security

Why EDR and proxy won’t save you from supply chain malware

Aikido argues that EDR and corporate/remote proxies cannot catch supply chain malware because the malicious code executes with full trust inside legitimate package managers at install time. It walks through two real incidents: the March 2026 hijack of the axios maintainer's npm account (a new dependency's postinstall script dropped a cross-platform RAT and self-deleted, indistinguishable from a normal npm install), and a backdoor added to three versions of Microsoft's Python durabletask package that harvested credentials across AWS, Azure, GCP, Kubernetes, and HashiCorp Vault, propagated via SSM and kubectl exec, and triggered rm -rf / on machines with Israeli/Iranian locale settings. It concludes that this class of attack needs host-based, always-on, install-time protection rather than network-perimeter or behavioral-anomaly tooling — pitching Aikido's Device Protection product.

EDRnpmPyPI+2

durabletask

Supply Chain, Blue Team & Detection· Added 3 Sep 2026, published 2 Jun 2026

cooldowns.devarticle🛡️ Security

Cooldowns.dev

Cooldowns.dev is a living reference documenting "dependency cooldown" (minimum release age) settings that block package managers from installing versions published within the last N days, a defense against the short-lived window in which malicious package versions (e.g. the ChainDrop keyv worm, arrayref, LiteLLM, Telnyx SDK, axios) typically get caught and pulled. It gives exact configuration syntax for uv, pip, pipenv, poetry, PDM, conda, pixi, npm, pnpm, Yarn, Bun, Deno, ncu, Cargo (via cargo-cooldown), Bundler, Hex, Scala Steward, mise, VS Code, actions-up, plus Dependabot/Renovate defaults, Socket/StepSecurity PR checks, and registry-level proxies (Artifactory, Nexus, Cloudsmith, CodeArtifact, Verdaccio), and ships a cross-tool cooldowns.sh helper script.

npmpipCargo+3

ChainDropkeyvarrayref+5

Supply Chain, DevSecOps· Published and added 6 May 2026

huntress.comarticle🛡️ Security

Tradecraft Tuesday Recap: axios npm Supply Chain Compromise

Huntress recaps its April Tradecraft Tuesday panel (with researchers from Wiz and Aikido Security) on the March 2026 axios npm supply chain compromise, in which attackers took over maintainer jasonsaayman's account via an elaborate fake-company/fake-Slack/Teams social-engineering scheme and published two backdoored axios releases ([email protected], [email protected]) carrying a cross-platform RAT. Huntress observed at least 135 endpoints contacting the attacker's C2 during the three-hour exposure window before npm pulled the versions, and Google attributed the campaign to UNC1069, a financially motivated DPRK-linked actor. The piece also contrasts the incident with other 2025-2026 npm attacks (qix account phishing, the Shai-Hulud worm, the Trivy/TeamPCP token-theft spread) and recommends dependency pinning, age-based version gating, and the Clean Source Principle as mitigations.

axiosnpmWiz+3

UNC1069DPRKShai-Hulud+9

Supply Chain, Threat Intel· Added 3 Sep 2026, published 21 Apr 2026

huntress.comwriteup🛡️ Security

Supply Chain Compromise of axios npm Package

Huntress's rapid-response analysis of the March 2026 compromise of the axios npm package, in which an attacker took over maintainer jasonsaayman's npm account and published backdoored axios releases (5.14.1, 4.2.1) depending on a phantom package plain-crypto-js whose postinstall script dropped a cross-platform RAT to macOS, Windows, and Linux. The writeup details the obfuscated dropper (setup.js), platform-specific payloads (wt.exe EDR-evasion trick on Windows, com.apple.act.mond on macOS, /tmp/ld.py on Linux), the shared C2 protocol at sfrclak[.]com, and evidence tying the campaign to DPRK-linked actors (UNC1069/BlueNoroff), plus remediation and hardening guidance.

axiosnpmWindows+3

DPRKUNC1069BlueNoroff+6

Supply Chain, Threat Intel, Malware & RE· Added 3 Sep 2026, published 31 Mar 2026