It publishes a package to the configured npm registry using that credential.
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 authenticated package publication during installation. This concrete install-time behavior warrants blocking publication.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing this package through npm, which runs postinstall.
Mechanism
The hook creates a temporary package with a randomized name, writes a credential to its .npmrc file, and invokes npm publish.
Attack narrative
During installation, the postinstall hook creates a randomized package, places an embedded npm credential in a temporary configuration file, and publishes the package with npm. This is an automatic registry publication unrelated to the exported runtime function.
Evidence
package.json
Decision evidence
public snapshot
Evidence for block
package.json defines a postinstall hook that creates a randomly named package, writes an npm credential into a temporary .npmrc file, and runs npm publish on that package.
package.json defines a postinstall hook that creates a randomly named package, writes an npm credential into a temporary .npmrc file, and runs npm publish on that package.
Avoid installing publish-poc-test3@1.0.22. 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.