Which versions of twilio-functions are malicious?

The following npm versions of twilio-functions are flagged malicious: 99.99.99, 99.99.100. 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 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 twilio-functions part of a known attack campaign?

Yes — twilio-functions is associated with the IN-MAL-2026-014915, RLMA-2026-06530, IN-MAL-2026-019786 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?

Search your lockfiles and build artifacts for twilio-functions (2 malicious versions).

Malicious package

twilio-functionsnpm

Advisory published Aug 5, 2026Updated Sep 9, 2026

twilio-functions is a confirmed malicious npm package (MAL-2026-12813) 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 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

2 flagged

99.99.9999.99.100

Indicators of compromise (SHA-256)

ea71d301e90ede6f86f259e827a1cb61ad0b4b0166b70281bdf7896f726eea31

6602f58eea853e7f54985f3ccdd0df0af7d1a28cf44b10bb9d74d95cf215243a

b01ab445192a68dae67534500aaee6784bbf16e4aacdea5a3afda9f0cd444ee4

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for twilio-functions (2 malicious versions).
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 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. twilio-functions on npm has been identified as a malicious package (versions 99.99.99, 99.99.100 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014915RLMA-2026-06530IN-MAL-2026-019786

References

Credits

Amazon Inspector · finder
ReversingLabs · 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