Contacts an unexplained external host during installation; no explicit payload is present in the command.
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 unconditional preinstall hook contacts an unexplained hard-coded host over HTTP. The command contains no explicit data payload, so this is install-time contact abuse rather than demonstrated data exfiltration.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install invokes the preinstall hook.
Mechanism
The hook runs curl against a hard-coded raw IP address over HTTP, with no user choice or consent check.
Attack narrative
During installation, the preinstall hook makes an unconditional HTTP request to a hard-coded IP address. The package provides no context for this endpoint, making this unauthorized install-time contact malicious.
Evidence
package.json
Network endpoints1
159.223.131.130:8080
Decision evidence
public snapshot
Evidence for block
The package runs an unconditional preinstall hook that curls http://159.223.131.130:8080 during installation.
Evidence against
The command supplies no explicit data payload or credentials.
The snapshot contains only package.json, so there is no further source context explaining the endpoint.
Avoid installing teick@1.0.1. 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.