The request sends no identifiable host, user, or project data, but performs unauthorized contact with an unrelated collector.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The manifest makes the webhook request reachable automatically during installation. Because the request contacts an unrelated collector without sending user or project data, this meets the install-time contact rule for install_hook_abuse.
Static reason
One or more suspicious static signals were detected.
Trigger
Automatically during package installation via the postinstall script.
Mechanism
The hook runs probe.js, which makes an HTTPS GET request to a webhook.site URL and suppresses request errors.
Attack narrative
During installation, the package's postinstall hook runs probe.js, which contacts a hard-coded webhook.site collector. The request carries no host, user, or project data, so this is unauthorized install-time contact rather than demonstrated data theft.
Evidence
package.jsonprobe.js
Network endpoints1
webhook.site/667bf650-8676-451a-8f55-b647d58825d7
Decision evidence
public snapshot
Evidence for block
The package runs `node probe.js` automatically in its postinstall hook.
`probe.js` sends an HTTPS request to a webhook.site collector during installation; the request contains no host, user, or project data.
Avoid installing sirens-lamentt@99.0.2. 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.