Which versions of twiliobox are malicious?

The following npm versions of twiliobox are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate twiliobox if I installed it?

twiliobox 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.

I already installed twiliobox — how do I know if it already compromised me?

If twiliobox was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is twiliobox part of a known attack campaign?

Yes — twiliobox is associated with the IN-MAL-2026-010515 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find twiliobox across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for twiliobox (version 1.0.0).

Malicious package

twilioboxnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

twiliobox is a confirmed malicious npm package (MAL-2026-10593) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in twiliobox (npm)

MAL-2026-10593

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall twiliobox

What this malware does

On npm install, [email protected] runs its declared postinstall script (node.init.js), which enumerates credential-shaped environment variables (NPM_TOKEN, AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, STRIPE, DB, SSH, GCP, Azure, etc.), reads ~/.npmrc, ~/.env*, and ~/.config/* files matching token/credential/secret patterns, and collects host identifiers (os.hostname, os.platform, process.cwd, pid). The harvested data is POSTed via https.request to a hardcoded third-party endpoint at webhook.cool/at/tender-deer-80/hG-DWynJKenViD9XWI5Mf8CulD0I9G2s. The package name resembles the well-known 'twilio' library, consistent with a typosquat lure. Installing this package on a developer or CI machine causes automatic transmission of installer-side secrets to an attacker-controlled webhook.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1a94eb66c6d3f03cf5b4e2e13527b9ab9bcb1ae85e75b62f79f58e225b941970

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for twiliobox (version 1.0.0).
If you installed it — respond
twiliobox 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 twiliobox was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. twiliobox on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010515

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks twiliobox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database