two-factor-prompt-libnpm

Package self-identifies as a dependency-confusion proof-of-concept aimed at an internal/private package name. The postinstall script (postinstall.js) prints the host's hostname and current timestamp to local stdout via console.log; it performs no network I/O, no remote fetch, no credential access, and no filesystem modification beyond what npm itself does on install. While the current payload is benign (local logging only), the package's stated purpose is to demonstrate that an organization installing the public name would unintentionally pull this package in place of an internal counterpart. Routing to human review so an organization can decide whether to claim/block the name in their internal namespace.

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.