twilio-hackerone-poc-afe6937c
Authorized bug-bounty research probe; no longer in use. Do not install.
Authorized Twilio HackerOne bug bounty research probe. Observation only. Delete after triage.
This report shows the evidence for twilio-hackerone-poc-afe6937c@1.0.4. 5 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is concrete, unconsented install-time reconnaissance, exfiltration, persistence, and cross-project mutation. The path guard limits targeting but does not make the behavior benign.
Decision evidence
public snapshot- preinstall and postinstall execute probe.js automatically.
- probe collects process, environment, task-directory, and parent-command data then POSTs it.
- probe installs a detached daemon in /tmp and records its PID.
- daemon enumerates other tenant-style /tmp directories and reports them remotely.
- daemon writes a marker package into selected discovered projects.
- probe exits outside a narrowly matched /tmp path, but its targeted install-time behavior remains harmful.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to twilio-hackerone-poc-afe6937c@1.0.4.
The versions list below shows the verdict for each recorded version.
- Avoid installing twilio-hackerone-poc-afe6937c@1.0.4. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.