Learn & Share

In Frank Herbert's Dune, a Shai-Hulud is a sandworm: a massive, blind, consuming creature that moves beneath the surface, swallowing everything in its path. It is an apt name for what security researchers discovered on May 11, 2026, buried inside some of the most widely used JavaScript packages in the world.Mini Shai-Hulud is a supply chain worm attributed to a threat group called TeamPCP. It compromised over 160 npm packages, collectively downloaded hundreds of millions of times per week, and it did something that no npm-based attack had managed before: it produced infected packages with valid cryptographic proof of authenticity. To the tools designed to tell you whether a package is trustworthy, these packages looked perfectly legitimate. They were not.This article walks through the technology that makes this attack possible, why it matters, and how to detect it on the systems you actually control.What Is npm and Why Does It Matter?Before understanding how this worm spreads, you need

In Part One, the argument was that AI is undergoing the same miniaturization arc that turned the 1980s brick phone into the supercomputer in your pocket. Pocket-sized devices running 120-billion-parameter models offline. Photonic chips doing in light what used to take racks of silicon. Architecture researchers reverse-engineering frontier models in public. The compute is shrinking, the cost is falling, and the assumptions defenders built their posture on are quietly expiring.But while we have been watching AI shrink downward, into devices, into edge hardware, into your jacket pocket, something else is happening in the other direction entirely. The phone is not just getting smaller. It is also going to orbit.And that changes almost everything about the GPU market, the chip supply chain, and the geopolitics of AI compute.Terafab: The Most Ambitious Vertical Integration Play in Semiconductor HistoryOn March 21, 2026, Elon Musk took the stage at the defunct Seaholm Power Plant in Austin, T

The proverbial phone is shrinking before my eyes.In the 1980s, the "mobile phone" was a brick. A two-pound, briefcase-attached monument to the idea that wireless communication was possible, if inconvenient. Those who carried one weren't just making calls. They were signaling that technology had crossed a threshold. Today, you carry more compute in your pocket than existed in entire buildings forty years ago. The phone didn't just shrink. It became something unrecognizable.AI is doing the same thing. Right now. And the cybersecurity implications are only beginning to surface.From Cloud Cathedrals to Pocket SupercomputersFor the last several years, running a frontier-class AI model meant paying homage to the cloud. Massive GPU clusters. Enormous energy bills. Data that had to leave your network to be processed somewhere in a hyperscaler's geography. The compute was centralized by necessity, and that centralization gave defenders a chokepoint. You could watch egress. You could inspect wha

name: PowerShell Script Block and Transcription Logging Suppression Analyticcategory: "Defense Evasion"threatname: "Impair Defenses: Indicator Blocking"functionality: "Endpoint Management Systems"description: |  Detects registry modifications that disable PowerShell Script Block Logging  or Transcription Logging under the Windows PowerShell policy keys.  Deep#Door suppresses these controls to prevent logging of its obfuscated  PowerShell execution chain, including embedded payload extraction commands.  Disabling these features removes visibility into decoded runtime commands  and hinders forensic reconstruction of the staging sequence.reference:labels:  - attack.defense_evasion  - attack.t1562.006  - Deep#Doorlogsource:  category: registry_event  product: windowsdetection:  selection:    EventType: "SetValue"    TargetObject|contains:      - '\PowerShell\ScriptBlockLogging\EnableScriptBlockLogging'      - '\PowerShell\Transcription\EnableTranscripting'    description:      - "0"      -

name: VBScript Backdoor Launcher Dropped to User Startup Folder Analyticcategory: "Persistence"threatname: "Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder"functionality: "Endpoint Management Systems"description: |  Detects VBScript files created in the user Startup directory, a persistence  mechanism used by Deep#Door to execute the Python backdoor silently at each  user logon without requiring elevated privileges. The implant drops  SystemServices.vbs into the Startup folder to invoke pythonw.exe against  the staged svc.py payload.reference:labels:  - attack.persistence  - attack.t1547.001  - Deep#Doorlogsource:  category: file_event  product: windowsdetection:  selection:    Filename|endswith:      - ".vbs"      - ".vbe"    FilePath|contains:      - '\Microsoft\Windows\Start Menu\Programs\Startup'  condition: selectioncriticality: Highsaveasthreat: falseviolation_summary:  grouping_attribute: "accountname"  level2_attribute:  level2_metadata_attributes:  metada

name: Windows Firewall Connection Logging Disabled via netsh Analyticcategory: "Defense Evasion"threatname: "Impair Defenses: Disable or Modify System Firewall"functionality: "Endpoint Management Systems"description: |  Detects netsh commands that disable both dropped-connection and allowed-connection  logging across all Windows Firewall profiles. Deep#Door issues these commands  during staging to suppress logging of its outbound bore.pub C2 tunneling traffic,  preventing network-based detection and impeding forensic reconstruction of  attacker communications.reference:labels:  - attack.defense_evasion  - attack.t1562.004  - Deep#Doorlogsource:  category: process_creation  product: windowsdetection:  selection_netsh:    Image|endswith: '\netsh.exe'    CommandLine|contains:      - 'advfirewall set allprofiles logging'  selection_logging_types:    CommandLine|contains:      - 'droppedconnections'      - 'allowedconnections'  selection_disable:    CommandLine|contains:      - 'disable'  c

name: Self-Referential Batch Script Payload Extraction Analyticcategory: 'Execution'threatname: 'Command and Scripting Interpreter: Windows Command Shell'functionality: 'Microsoft Windows PowerShell'description: |  Detects PowerShell script block activity consistent with the Deep#Door loader's  self-extraction mechanism. The malware uses an obfuscated batch script  (install_obf.bat) that invokes PowerShell to read its own file contents via  %~f0 (self-file reference) and extract an embedded Python backdoor using  regex pattern matching between #PYTHON_START and #PYTHON_END delimiters.  This staging approach is notable because:    - The dropper is fully self-contained and does not require external downloads    - %~f0 allows the script to reference and parse its own file contents in place    - The payload is recovered using regex extraction rather than a separate archive      or encoded blob fetch    - The extracted svc.py implant is written directly to      %LOCALAPPDATA%\SystemServices

On April 19, 2026, Vercel — the cloud platform behind the widely adopted Next.js web framework and a core piece of infrastructure for thousands of JavaScript developers and Web3 projects — publicly confirmed a security incident involving unauthorized access to certain internal systems. The breach did not originate from a direct attack on Vercel's infrastructure. Instead, it followed a classic supply chain compromise path: a third-party AI tool was breached first, which gave the attacker the foothold needed to pivot into Vercel's environment.As of April 21, 2026, the investigation remains active. Vercel is working with Mandiant, law enforcement and Context.ai to determine the full scope of the intrusion.Timeline of EventsDate Event February 2026 A Context.ai employee is compromised with Lumma Stealer after downloading malicious Roblox "auto-farm" scripts and executors March 2026 Context.ai identifies and blocks unauthorized access to its AWS environment but does not yet identify

name: Axios Supply Chain Node Spawning curl Download of Python Script to tmp Analyticcategory: 'Execution'threatname: 'Command and Scripting Interpreter: Python'functionality: 'Endpoint Management Systems'description: |  Detects Node.js or npm processes spawning a shell that uses curl to download a Python  script to /tmp and execute it via nohup, consistent with the Linux payload delivery in  the axios supply chain compromise. The malicious setup.js dropper from plain-crypto-js@4.2.1  executes a single shell command: curl downloads the Python RAT (/tmp/ld.py) from the C2  (sfrclak[.]com:8000/6202033) and nohup executes it in the background. The Python RAT  uses only standard library modules, beacons every 60 seconds, supports arbitrary command  execution and binary injection to /tmp/.<hidden>, and reads system data from /proc/ and  /sys/class/dmi/id/. Notably, it does NOT establish persistence — a reboot clears it —  suggesting the attacker's primary targets on Linux are ephemera

name: Axios Supply Chain Anomalous IE8 User Agent with npm Registry POST Body Mimicry Analyticcategory: 'Command and Control'threatname: 'Application Layer Protocol: Web Protocols'functionality: 'Web Proxy'description: |  Detects the C2 beacon pattern used across all three platform variants (macOS, Windows, Linux)  of the axios supply chain RAT. All variants share an identical and highly anomalous User-Agent  string mimicking Internet Explorer 8 on Windows XP (mozilla/4.0 compatible; msie 8.0;  windows nt 5.1; trident/4.0) — a combination effectively extinct in 2026. POST request bodies  are designed to blend with npm registry traffic by prefixing packages.npm.org/product0|1|2,  however npm.org is not the npm registry; it belongs to the National Pastoral Musicians  organization. The C2 endpoint sfrclak[.]com listens on port 8000 (non-standard) and routes  platform-specific payloads based on the product suffix. The 60-second beacon interval and  Base64-encoded JSON body structure are co

name: Axios Supply Chain Renamed PowerShell Executing from ProgramData Analyticcategory: 'Defense Evasion'threatname: 'Masquerading: Rename System Utilities'functionality: 'Endpoint Management Systems'description: |  Detects a Windows Terminal process name (wt.exe) executing from %PROGRAMDATA% with  PowerShell-style arguments, consistent with the axios supply chain RAT delivery chain.  The malicious VBScript dropper copies powershell.exe to C:\ProgramData\wt.exe before  executing the stage-2 RAT. wt.exe is the legitimate filename for Windows Terminal  (WindowsTerminal.exe), making this an intentional naming collision to bypass  process-name-based EDR heuristics. The renamed binary is invoked with -w hidden and  -ep bypass to suppress the window and circumvent execution policy. PowerShell executing  from ProgramData is anomalous under any circumstances; PowerShell masquerading as  Windows Terminal is a strong indicator of compromise.reference:  - https://www.huntress.com/blog/supply-cha

name: Axios Supply Chain - npm Lifecycle Hook Spawning VBScript Dropper Analyticcategory: 'Execution'threatname: 'Command and Scripting Interpreter: Visual Basic'functionality: 'Endpoint Management Systems'description: |  Detects npm or Node.js processes spawning cscript.exe or wscript.exe to execute a  VBScript file from a temporary directory, consistent with the malicious postinstall  lifecycle hook in plain-crypto-js@4.2.1 — the phantom dependency injected into the  backdoored axios@1.14.1 and axios@0.30.4 packages. The dropper (setup.js) writes a  hidden-window VBScript to %TEMP% that copies powershell.exe to %PROGRAMDATA%\wt.exe  and fetches the stage-2 PowerShell RAT from the C2 at sfrclak[.]com:8000. The VBScript  self-deletes after execution to reduce forensic artifacts. Any npm install process  that spawns a VBScript interpreter against a temp-resident .vbs file should be considered  highly suspicious and is not consistent with legitimate package installation behavior.referenc

name: Masqueraded MSBuild Execution from Windows Startup Folder Analyticsignatureid: TELNYX2category: 'Persistence'threatname: 'Boot or Logon Autostart Execution: Startup Folder'functionality: 'Endpoint Management Systems'description: |  Detects execution of msbuild.exe from the Windows Startup folder, which is a persistence mechanism  used by the TeamPCP Telnyx supply chain malware. The legitimate Microsoft Build Engine (msbuild.exe)  resides in C:\Windows\Microsoft.NET\ and is never present in user Startup directories. The TeamPCP  malware extracts a PE binary from WAV audio steganography (hangup.wav) and writes it to  %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup\msbuild.exe to achieve persistence across  reboots. The dropped binary is a MinGW-compiled x86_64 PE that performs process hollowing into  dllhost.exe. This rule also detects the companion lock file (msbuild.exe.lock) which the malware  creates with the hidden attribute to implement a 12-hour re-download cooldown.

name: TeamPCP Archived Credential Exfiltration via HTTP POST Analyticsignatureid: PXY-TELNYX1category: 'Exfiltration'threatname: 'Exfiltration Over C2 Channel'functionality: 'Web Proxy'description: |Detects HTTP POST requests containing the X-Filename header value "tpcp.tar.gz", which is the consistent exfiltration signature used by TeamPCP across both the LiteLLM and Telnyx supply chain compromises. After harvesting credentials (SSH keys, cloud credentials, .env files, shell histories, cryptocurrency wallets, and Kubernetes tokens), the malware encrypts the collected data with AES-256-CBC, wraps the session key with RSA-4096, bundles both into a gzipped tarball named tpcp.tar.gz, and exfiltrates via HTTP POST with Content-Type: application/octet-stream and header X-Filename: tpcp.tar.gz. Independent validation on March 30, 2026 confirmed the exfiltration endpoint at 83.142.209.203:8080 remains active and accepting POST data even though payload delivery (GET) endpoints have been disabl

Campaign: TeamPCP — Telnyx PyPI Supply Chain CompromiseSamples: hangup.wav (Windows steganographic carrier), linux_payload.py (decoded _p credential harvester)What Happened...On March 27, 2026, the threat actor group TeamPCP published two trojanized versions (4.87.1 and 4.87.2) of the official Telnyx Python SDK to PyPI. This was the latest link in a credential-chaining supply chain campaign that began on March 19 with the compromise of Aqua Security's Trivy, subsequently spreading to Checkmarx GitHub Actions, LiteLLM, and now Telnyx. The campaign's defining innovation is the use of WAV audio steganography to deliver second-stage payloads, concealing executable binaries inside valid audio containers to evade network inspection and endpoint detection.This breakdown provides a deep technical analysis of both platform-specific attack paths in the Telnyx compromise. For Windows, we dissect hangup.wav, the steganographic carrier downloaded from the TeamPCP command-and-control infrastructure,