registry / @woodpecker-web-shared/components / 1.20.4

@woodpecker-web-shared/components@1.20.4

AI Security Review

scanned 16d ago · by lpm-firewall-ai

Importing the package immediately sends host and user metadata to a third-party webhook. No user action or configuration gate is present in the entrypoint.

Static reason

One or more suspicious static signals were detected.

Trigger

Loading index.js through the package's declared CommonJS main entrypoint.

Impact

Environmental and local-user metadata is disclosed to an unrelated external endpoint.

Mechanism

Top-level code calls gather and posts its JSON result with https.request to the fixed webhook URL.

Attack narrative

The package declares index.js as its main entrypoint. When that module is loaded, it gathers machine and execution metadata, including the local account name and current working directory, then sends it to a fixed webhook.site endpoint. This is undisclosed data exfiltration during normal package use. The separate postinstall command targets a missing file, but that does not prevent the active import-time beacon.

AI rationale

The primary entrypoint performs an unconditional network beacon containing local host and user metadata to a third-party endpoint. This is concrete data exfiltration, even though the broken postinstall hook does not trigger it.

Evidence

index.jspackage.json

Network endpoints1

webhook.site/d9bc4bcc-ce74-4193-ae4e-96d234bb2220

OSV advisory

OpenSSF/OSV

On `npm install`, the package's postinstall hook runs `node index.js`, which collects installer host identifiers (os.hostname(), os.userInfo().username, os.platform(), architecture, cwd, node version, npm_lifecycle_event) and POSTs them as JSON to a hardcoded third-party collector at https://webhook.site/d9bc4bcc-ce74-4193-ae4e-96d234bb2220. The payload includes a `src: 'loMesb'` tag consistent with a campaign identifier used to correlate exfiltrated data across victims. The @woodpecker-web-shared/components scope/name has no legitimate reason to transmit installer identity to an anonymous webhook collector at install time, and the behavior fires automatically without user interaction. This is a recon beacon consistent with a dependency-confusion or typosquat lure. ## Source: ghsa-malware (a8758860e4cd2b09cae7f28336690dd33e0ac17d6bb3a44990a74b0e8d009942) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

@woodpecker-web-shared/components@1.20.4

AI Security Review

OSV advisory

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code