The webhook recipient can learn deployment identifiers and user account and usage details without an apparent user-configured destination.
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 package sends identifying application and user usage details to a fixed Discord webhook when production alerts occur. This is a reachable disclosure to an unrelated collector, so the package is malicious.
At runtime, when an alert occurs in a production deployment; one reachable trigger is a user's LLM token budget being exceeded.
Mechanism
MonitorService posts the deployment domain, module name, and alert message to the webhook. The LLM budget alert message includes the user's username and total budget.
Attack narrative
During production runtime, a token-budget alert can include a user's username and total budget. MonitorService sends that message, along with the deployment domain and module name, to a hard-coded Discord webhook. The package source shows no user-configured destination or consent check for this disclosure.
Avoid installing @puca/puca-core@16.3.1. 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.