NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

building-buildnpm

Advisory published Updated

building-build is a confirmed malicious npm package (MAL-2026-17164) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in building-build (npm)

MAL-2026-17164
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall building-build

What this malware does

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.

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.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

4618f06d0398ff90ef90003464e79f23609a160f4d1606f60cf797fb73fa6dcb
847ce0ff3120a15a7a4d872e3a00f22f1917a828ca61d5767a0b24d36b933aa0

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for building-build (version 1.0.0).

  2. If you installed it — respond

    Remove building-build from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If building-build was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. building-build on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020516GHSA-2fq4-2r26-qr64

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks building-build-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

building-build (npm) malicious package — MAL-2026-17164 | O3 Security