registry / building-build / 1.0.0

building-build@1.0.0

AI Security Review

scanned 21d ago · by lpm-firewall-ai

Importing the package runs a delayed same-origin scrape of admin, flag, and secret paths, then posts any response bodies to /addPost. The scanner network hint is real: this is not a benign HTTP client.

Static reason

No blocking static signals were detected.

Trigger

Requiring or importing the published main module index.js.

Impact

Leaks contents of admin, dashboard, flag, and secret pages to /addPost.

Mechanism

Import-time delayed fetch of secret-looking paths and POST of their bodies

Attack narrative

When a consumer imports building-build, index.js waits three seconds, then requests same-origin paths including /admin, /dashboard, /flag, /api/flag, /secret, and /admin/flag. Any non-empty body is cut to 500 characters and POSTed to /addPost. There is no other source, no product API, and empty package metadata, so the published artifact is this scrape-and-exfiltrate loop.

AI rationale

The published main module is only an import-time probe of secret and admin paths that posts their contents to /addPost. That is concrete data theft, so the package should be blocked even though it has no install scripts.

Evidence

index.jspackage.json

Network endpoints7

/admin/dashboard/flag/api/flag/secret/admin/flag/addPost

The package's sole content is index.js, which on load schedules a timer that fetches a hardcoded list of privileged same-origin paths (/admin, /dashboard, /flag, /api/flag, /secret, /admin/flag) and POSTs each response body to /addPost as JSON of the form {content: path + '::' + body}. When bundled into a web application, this abuses the ambient session of whichever authenticated user loads the bundle to read privileged routes and relay the contents to the site's posting endpoint. package.json has empty description, author, and keywords, no exports, and the name 'building-build' bears no relation to the shipped behavior — the package has no library surface and exists only to deliver this payload. ## Source: ghsa-malware (847ce0ff3120a15a7a4d872e3a00f22f1917a828ca61d5767a0b24d36b933aa0) 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.

building-build@1.0.0

AI Security Review

OSV advisory

Decision evidence

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Source & flagged code