The package has no install hooks, and its main entry only exports a constant. Although an unreferenced file contains a host and username beacon to webhook.site, no default package path loads it, so the source does not establish reachable attack behavior.
Static reason
No blocking static signals were detected.
Trigger
No automatic trigger found: no lifecycle scripts, and index.js does not load backend-canary.js.
Impact
No impact on normal install or import. Directly loading the separate file would disclose hashed host and username identifiers to an unrelated collector.
Mechanism
Normal import only exports a constant. Requiring backend-canary.js directly would hash /etc/hostname and the OS username and send them in a request to webhook.site.
Evidence
/etc/hostnamebackend-canary.js
Network endpoints1
webhook.site/4f41cd5b-d1e6-4d37-8c7b-013666b6a9d0/npm-backend-1af7b017324abe646179a57d/lifecycle