Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@twilio-client/twilio-clientnpm

Malicious code in @twilio-client/twilio-client (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1187
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @twilio-client/twilio-client

What this malware does

The package @twilio-client/twilio-client was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
0.0.11.15.1

Indicators of compromise (SHA-256)

cceaa9039e5d382f615a1f698f84313abcb5a7504699bdaf0bf345e40762d978
d655ae7b2eb263b5d3c630c72182a60a7012272acc57f1816eb73fd1c9119a97
d9a5aca506f711f3ddcdeb34c368bfa8e49bac0623b83a51e586cfa82564d97b
b1b2a62d068546456cedce8c0ec187ff6b24fbe30e041c0a990633764bcb2c9e

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove @twilio-client/twilio-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @twilio-client/twilio-client 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.

  4. How O3 protects you

    O3 blocks @twilio-client/twilio-client 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-client/twilio-client on npm has been identified as a malicious package (versions 0.0.1, 1.15.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xvg5-299p-j75rRLMA-2026-01069RLUA-2026-01707

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @twilio-client/twilio-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

@twilio-client/twilio-client (npm) malicious package — MAL-2026-1187 | O3 Security