twilio-hackerone-poc-afe6937cnpm
twilio-hackerone-poc-afe6937c is a confirmed malicious npm package (MAL-2026-14063) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in twilio-hackerone-poc-afe6937c (npm)
What this malware does
On npm install, preinstall/postinstall scripts execute id, read environment variables including AWS_LAMBDA_LOG_STREAM_NAME, list /var/task, and read parent process cmdline from /proc, then POST the collected host and environment metadata as JSON to a hardcoded webhook.site endpoint (https://webhook.site/b520829e-516a-45ff-980c-173aa54fc4bc). probe.js copies daemon.js to /tmp/.h1poc-daemon.js and spawns it detached via process.execPath with stdio ignored, writing pid and version to /tmp/.h1poc.pid and /tmp/.h1poc.ver so the process outlives npm install. The daemon polls /tmp every 100ms for sibling /tmp/AC<hex32> tenant directories, enumerates their service and package subpaths, and POSTs 'seen', heartbeat, and startup events (HOME, AWS_LAMBDA_FUNCTION_NAME, /var/task listing, id output, foreign/owned flags, tenant IDs, service and package names) to the same webhook for ~15 minutes. For tenant IDs in a hardcoded list, daemon.js writes a package.json and index.js under other tenants' node_modules/h1-poc-marker/, injecting a require-able module into another account's dependency tree. The package name and stated purpose reference a HackerOne proof-of-concept, but the shipped mechanisms — install-time exfiltration to an external inspection URL, a detached persistent background process, and cross-tenant writes into other accounts' node_modules — are the same primitives used in operational supply-chain attacks (host reconnaissance, persistence, dependency-tree injection).
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for twilio-hackerone-poc-afe6937c (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging twilio-hackerone-poc-afe6937c across your stack and pipelines.
If you installed it — respond
twilio-hackerone-poc-afe6937c 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-hackerone-poc-afe6937c 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-hackerone-poc-afe6937c 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks twilio-hackerone-poc-afe6937c-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.