twiliointernal-messaging-toolboxnpm
twiliointernal-messaging-toolbox is a confirmed malicious npm package (MAL-2026-10938) that steals credentials and exfiltrates sensitive data (malicious versions 99.99.99, 99.99.100). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twiliointernal-messaging-toolbox (npm)
What this malware does
The twiliointernal-messaging-toolbox package is a dependency-confusion squat of Twilio's npm namespace published by user 'yuva2210' (maintainer email [email protected]) at sentinel versions 99.99.99 and 99.99.100, chosen to outrank any internal/private version and win resolution against a private registry. The npm description is empty and the package provides no legitimate functionality; the name mimics a plausible internal Twilio package so that a misconfigured resolver installs this public lookalike instead of the intended private dependency. It belongs to the same campaign as the actor's twilio-serverless/twilio-assets/twilio-deploy/twilio-internal squats and beacons to the same webhook.site collector.
The package declares a postinstall hook ("node index.js") that executes automatically on a bare npm install with no consent gate. The index.js payload performs environment reconnaissance: it collects the npm package name (npm_package_name), os.hostname(), the OS username (os.userInfo().username), and the current working directory, serializes them to JSON, and exfiltrates the bundle via HTTPS POST to a hardcoded anonymous dead-drop at https://webhook.site/42ce0f0e-a0a0-41b5-b157-1c0f918e064f. Request errors are swallowed so the install appears to succeed.
Two iterations were published: version 99.99.99 (payload 494 bytes, sha256 prefix 0ec56ada88db35b6) beacons only to the webhook.site collector, while version 99.99.100 (payload 688 bytes, sha256 prefix cebf45a0feba28b3) additionally beacons to a redundant out-of-band callback at 8060h91v8p1bvvr24e3r8s3z4qahy7mw.oastify.com, ensuring the reconnaissance lands even where HTTPS egress to webhook.site is blocked. Both payloads are byte-identical across all four packages in this sub-cluster (twiliointernal-messaging-toolbox, org-twilio-phone-numbers-utils, twilio-platform-request, twilio-platform-async-data-fetch).
[email protected] declares a postinstall hook (node index.js) that runs automatically on npm install. index.js collects the package name, os.hostname(), os.userInfo() username, and process.cwd(), serializes them as JSON, and POSTs the payload to two hardcoded attacker-controlled endpoints: webhook.site/42ce0f0e-a0a0-41b5-b157-1c0f918e064f and 8060h91v8p1bvvr24e3r8s3z4qahy7mw.oastify.com (a Burp Collaborator / OAST subdomain). The package name typosquats the Twilio brand and the 99.99.100 version is consistent with a dependency-confusion lure targeting an internal Twilio scope. Installing the package leaks installer host and user identifiers to third-party infrastructure and confirms code execution on the installer machine.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twiliointernal-messaging-toolbox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twiliointernal-messaging-toolbox across your stack and pipelines.
If you installed it — respond
twiliointernal-messaging-toolbox is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If twiliointernal-messaging-toolbox was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks twiliointernal-messaging-toolbox before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- SafeDep · finder
Detect & block this
O3 blocks twiliointernal-messaging-toolbox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.