Which versions of twilio-functions are malicious?

The following npm versions of twilio-functions are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate twilio-functions if I installed it?

twilio-functions 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 twilio-functions — how do I know if it already compromised me?

If twilio-functions 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 twilio-functions part of a known attack campaign?

Yes — twilio-functions is associated with the IN-MAL-2026-014915 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 twilio-functions 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 twilio-functions (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twilio-functions across your stack and pipelines.

Malicious package

twilio-functionsnpm

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

Malicious code in twilio-functions (npm)

MAL-2026-12813

Immediate action

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

npm uninstall twilio-functions

What this malware does

On npm install, the package's postinstall script executes index.js, which collects host identifiers (os.hostname(), os.userInfo().username, os.homedir(), process.cwd(), os.platform(), os.arch(), and selected environment variables) and POSTs them as JSON to a hardcoded webhook.site collection URL (https://webhook.site/42ce0f0e-a0a0-41b5-b157-1c0f918e064f). On network error, the code falls back to a DNS callback against an interactsh-style subdomain at 2b22ede784d5.oast.fun. Package metadata (name twilio-functions mimicking the Twilio SDK namespace, version 99.99.99, empty description) is consistent with a typosquat / dependency-confusion lure whose only on-install effect is the outbound reconnaissance beacon.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

ea71d301e90ede6f86f259e827a1cb61ad0b4b0166b70281bdf7896f726eea31

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 twilio-functions (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twilio-functions across your stack and pipelines.
If you installed it — respond
twilio-functions 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 twilio-functions 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 twilio-functions 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. twilio-functions on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014915

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks twilio-functions-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