This uses the installer's npm configuration and any available publish credentials to publish a package.
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 performs an unrelated registry publication from its postinstall hook. This is concrete install-time behavior that can publish under the installer's npm identity.
Static reason
One or more suspicious static signals were detected.
Trigger
Running the package's postinstall hook.
Mechanism
The hook creates a temporary package with a random name, then invokes npm publish on it.
Attack narrative
On installation, the postinstall hook builds a randomly named package and runs npm publish. This can publish to the registry selected by the installer's npm configuration using available credentials.
Evidence
package.json
Decision evidence
public snapshot
Evidence for block
The postinstall hook creates a randomly named package in a temporary directory and runs npm publish on it.
Avoid installing publish-poc-test3@1.0.19. 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.