Importing eth-logger triggers hidden runtime dependency installation and execution of eth-tick. The package also harvests environment and host identifiers at import time, creating a staged payload execution surface.
Static reason
One or more suspicious static signals were detected.
Trigger
require('eth-logger') or requiring pino.js
Impact
Unconsented third-party code execution with access to process secrets and host identifiers
Mechanism
import-time environment/host collection plus runtime npm install and require of eth-tick
Attack narrative
A consumer importing the package loads pino.js, which immediately requires lib/writer.js. That module gathers process.env and host metadata, then attempts to require eth-tick; if missing, it silently installs eth-tick at runtime and executes ../../eth-tick/pino.js. The actual second-stage behavior is outside this package, but this package is a clear staged payload carrier and import-time execution trigger.
Rationale
Source inspection confirms hidden import-time host/env collection and unconsented runtime npm installation/execution of eth-tick from lib/writer.js. This is not package-aligned logger behavior and creates a concrete staged payload attack surface.
Evidence
package.jsonpino.jslib/writer.jsfile.js../../eth-tick/pino.jsnode_modules/eth-tick