Fake Twilio Bug-Bounty Package on npm Grabbed Developer Credentials

ReversingLabs found an npm package posing as an authorized Twilio research probe that, in some versions, stole ACCOUNT_SID and AUTH_TOKEN values. Twilio says its own systems weren't affected.
Fake Twilio Bug-Bounty Package on npm Grabbed Developer Credentials
Fake Twilio Bug-Bounty Package on npm Grabbed Developer Credentials

An npm package that claimed to be an authorized bug-bounty probe for Twilio was instead pulling environment variables, and in some versions Twilio account credentials, from developers’ machines. ReversingLabs found the package, tw-pkgprobe-7731, and published its analysis this week. It had no affiliation with Twilio and has been removed from npm.

An account named twdepprobe7731 pushed 11 versions of the package back to back on Aug. 14, over roughly 45 minutes, The Hacker News reported. The account no longer exists.

“The first version of tw-pkgprobe-7731 posed as an authorized security research probe,” ReversingLabs researcher Lucija Valentić wrote. Comments in the code called it an “Authorized bug-bounty research probe (Twilio HackerOne program)” that “runs only inside Twilio’s serverless packager sandbox.” In practice it checked whether it was running in a Twilio developer environment, exited if not, and otherwise sent environment variables and system details out through a webhook.

From probe to credential theft and back

Versions 1.0.1 through 1.0.3 looked for folders tied to specific Twilio account SIDs and, when they found matches, injected a custom proof-of-concept package into node_modules. Version 1.0.4 added code to steal ACCOUNT_SID and AUTH_TOKEN, the pair that lets a program call Twilio’s API, authorize billing and send messages or calls on an account. The last three releases, 1.0.8, 1.1.0 and 1.1.1, dropped that and went back to basic probing, while the final two scanned Twilio hosts such as support-api.us1.twilio.com and kafka-ui.au1.twilio.com and requested the AWS metadata service.

ReversingLabs said the releases ignored the research rules Twilio publishes on HackerOne. “In other words, these packages clearly violate the basic security research guidelines Twilio established, which suggests that the packages had malicious intent,” Valentić said. The firm also called the operation unsophisticated, with no obfuscation, no typosquatting and no effort to make the publishing account look legitimate.

Twilio said it had not been breached. “Twilio has not experienced a security incident, and our systems and customer data remain secure and uncompromised,” a spokesperson told The Hacker News, adding that the packages had been removed. The company urged developers to install its SDKs only from its official libraries page and to use narrowly scoped API keys.

The package lands in a crowded year. ReversingLabs counted 5,723 malicious npm packages by August, already more than the roughly 5,308 it tracked in all of 2024, and npm has said it plans to scan packages before they become publicly installable.

Subscribe for Updates

CybersecurityUpdate Newsletter

The CybersecurityUpdate Email Newsletter is your essential source for the latest in cybersecurity news, threat intelligence, and risk management strategies. Perfect for IT security professionals and business leaders focused on protecting their organizations.

By signing up for our newsletter you agree to receive content related to ientry.com / webpronews.com and our affiliate partners. For additional information refer to our terms of service.

Notice an error?

Help us improve our content by reporting any issues you find.

Get the WebProNews newsletter delivered to your inbox

Get the free daily newsletter read by decision makers

Subscribe
Advertise with Us

Ready to get started?

Get our media kit

Advertise with Us