It can publish an unauthorized package using the installer's active npm configuration and credentials.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
AI security review
scanned · by lpm-firewall-ai
The postinstall hook performs an automatic npm publish of a generated package, establishing unconsented install-time publishing behavior. This warrants blocking publication.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package, which runs its postinstall hook.
Mechanism
The hook writes a package manifest, constructs and executes an npm publish command, then removes the temporary directory.
Attack narrative
On installation, the postinstall hook creates a package with a randomized name and publishes it using npm. This can use the installer's active npm configuration and credentials to publish a package without a separate user action.
Evidence
package.json
Decision evidence
public snapshot
Evidence for block
package.json runs a postinstall hook that creates a package with a randomized name and invokes npm publish on it, causing an automatic package publication during installation.
package.json runs a postinstall hook that creates a package with a randomized name and invokes npm publish on it, causing an automatic package publication during installation.
Avoid installing publish-poc-test3@1.0.18. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.