MAL-2026-20260: Malicious code in sirens-lamentt (npm)
--- -= Per source details. Do not edit below this line.=-
Source: amazon-inspector (4b022b670038d31953a284f80705da79687f5a5e5b2706f61a99e2fe9fafde4a) sirens-lamentt@99.0.2 declares a postinstall lifecycle hook that unconditionally issues an HTTPS GET to a hardcoded webhook.site URL (https://webhook.site/667bf650-8676-451a-8f55-b647d58825d7) with a query string tagged source=htb-postinstall. The callback fires automatically on npm install, reporting the installer's IP address and install event to a third-party anonymous collector endpoint. The implausibly high version number (99.0.2) and the presence of a webhook.site beacon are consistent with a dependency-confusion probe targeting an internal package name.
Affected Software
Event History
Frequently Asked Questions
What happens when the affected package is installed?
Its postinstall lifecycle hook automatically sends an HTTPS GET request to a hardcoded webhook.site endpoint. The request is tagged with source=htb-postinstall and reports the installer's IP address and that an installation occurred.
Who is exposed to this behavior?
Any environment that runs npm install and resolves sirens-lamentt version 99.0.2 is exposed, because the callback is unconditional. This includes automated build or deployment environments if they install the package.
Does exploitation require an attacker to interact with the application after installation?
No. The network callback is triggered automatically during npm installation through the postinstall hook; no application runtime interaction is described.
What can be checked to identify prior exposure?
Check dependency manifests, lockfiles, npm installation records, and build logs for sirens-lamentt@99.0.2. Network logs may also show HTTPS requests to webhook.site/667bf650-8676-451a-8f55-b647d58825d7 with the source=htb-postinstall query tag.