Malicious npm package posed as a Twilio bug-bounty tool

Security researchers disclosed on 22 September 2026 that a malicious package on the npm registry, the main repository for JavaScript and Node.js code libraries, was posing as a security tool for developers building on Twilio. According to a report published by The Hacker News, the package, named "tw-pkgprobe-7731", presented itself as a bug-bounty probing utility while stealthily attempting to harvest sensitive data from the machines that installed it.

The report says the package was first uploaded to npm in mid-August 2026 by an account called "twdepprobe7731". That gave it roughly a month on the registry before the disclosure. The researchers describe the package as targeting developers who integrate Twilio, the cloud communications provider, into their applications. Twilio is not the source of the package, and the name appears to have been chosen to borrow credibility from the brand.

The core risk is credential theft. Researchers say the package was built to exfiltrate sensitive information, which in a developer environment typically means the secrets that sit closest to hand during installation. No figures for download counts, victim numbers or confirmed compromises were given in the disclosure, and the status of the incident is reported rather than confirmed damage.

The framing matters for teams running AI coding assistants and autonomous build agents. Package installation is one of the few moments when untrusted third-party code runs with the same privileges as the developer or the agent doing the work. An agent asked to "find a tool to test our Twilio integration" will search a registry, read a package description and install what looks plausible. A package that advertises itself as a security probe for a named vendor is well tuned to that behaviour, whether the reader is a human or a model.

The naming pattern is worth noting on its own. Both the package and the publishing account used a shared numeric suffix, 7731, which the researchers flagged as part of the same operation. Registry accounts created solely to publish a single lookalike package are a recurring shape in supply chain reports, and that shape is something automated review can be told to look for.

The practical mitigations are unglamorous. Teams can pin dependencies to reviewed versions, block post-install scripts by default, and run installs in containers that hold no long-lived cloud or messaging credentials. Where agents are permitted to add dependencies, a human approval step before a new package enters a lockfile removes most of the attack surface described here. Developers who installed tw-pkgprobe-7731 should treat any credential present on that machine as exposed and rotate it.