tw-pkgprobe-7731 v1.1.1, the campaign's final release, completes the network-mapping pivot. Armando found that probe.js probes a focused set of internal Twilio hosts and now posts the full connectivity map -- resolved IPs, open ports, HTTP status codes, server headers, and response snippets -- to a webhook. The AWS metadata request from v1.1.0 is removed, and only the postinstall hook remains.
Key Findings
- Malicious version: v1.1.1, published 2026-08-14 19:56 UTC; the last of the eleven releases
- Entry point: the
postinstall hook runs probe.js
- Targets: Twilio's internal hosts, reachable from the build sandbox
- Behavior: resolves DNS and tests TCP/443 plus an HTTPS GET against 12 internal Twilio hosts and an internal IP, then posts the resolved IPs, open ports, status codes, server headers, and body snippets to a webhook; the AWS metadata request is removed
- Detection: Script-JS.PUA.SupplyChain (probe.js), Text.PUA.SupplyChain, Archive-GZIP.PUA.SupplyChain, Archive-TAR.PUA.SupplyChain
Package Background
tw-pkgprobe-7731 was published by the npm account twdepprobe7731, whose maintainer address is npmpub7731hackerone@whatisthisington.com. It advertises itself as an "Authorized security research probe (bug bounty). No-op outside the specific sandbox it was written for." The package has no source repository, no dependencies, and no genuine functionality: its main file, index.js, exports an empty object in every release. All eleven versions were published on August 14, 2026 between 19:13 and 19:56 UTC, iterating every few minutes, and the package has since been removed from npm.
The target is not whoever installs the package by mistake. Every release begins by checking that the current working directory matches the pattern of a Twilio Serverless packager sandbox -- a temporary build directory whose name is a Twilio Account SID. Anywhere else, including an ordinary developer machine, the code does nothing. It runs only inside Twilio's own shared build infrastructure, where a single container packages functions belonging to many different Twilio customers side by side.