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

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twiliobox (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twiliobox across your stack and pipelines.

Malicious package

twilioboxnpm

Malicious code in twiliobox (npm) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twiliobox (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twiliobox across your stack and pipelines.
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 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 twiliobox 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

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