This attempts an unrequested publication using the installer's npm context.
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 package manifest contains an automatic postinstall command that creates a separate package and runs npm publish on it. This is concrete install-hook abuse, so publication should be blocked.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its postinstall hook.
Mechanism
The hook creates a temporary package and invokes npm publish on it.
Attack narrative
On installation, the postinstall hook creates a temporary package with a generated name and invokes npm publish on it. This attempts an unrequested publication using the installer's npm context.
Evidence
package.json$d/package.json$d/.npmrc
Decision evidence
public snapshot
Evidence for block
The postinstall hook creates a temporary package with a generated name, writes a local npm configuration file, and runs npm publish on that directory.
Avoid installing publish-poc-test3@1.0.21. 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.