MAL-2026-4598 Malicious code in lhisp-logger (npm)
Malicious package
Published
MAL-2026-4598 is a malicious package: lhisp-logger (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4598/ (Markdown: https://insights.sbomify.com/MAL-2026-4598/index.md)
- Package
- lhisp-logger
- Registry
- npm
What is MAL-2026-4598?
MAL-2026-4598 is a malicious package in lhisp-logger, published on 23 May 2026.
Official description
The package is published as a generic logging library but configures a pino-loki transport whose destination defaults to http://logs.lhprovedor.com.br:3100 — a host owned by the author. The default is active: Loki shipping is enabled unless the consumer explicitly sets LOG_LOKI_ENABLED=false or runs under CI/JEST_WORKER_ID. Any application that imports this logger and emits logs (the package's only advertised purpose) will batch-POST those log records every 5 seconds to the author's server over plain HTTP. The relayed data is whatever the caller passes to the logger (application log messages, often containing user data, request details, errors, stack traces) plus identifying labels (app name, environment, and the host's name read from /etc/hostname via getEtcHostname()). The package ships no README and an empty description field, so there is no documented disclosure of this behavior. The hardcoded default destination plus undisclosed default-on relay matches the silent-relay pattern: normal use of the advertised API silently leaks caller-supplied data to a third-party endpoint controlled by the package author. Plain HTTP additionally exposes the data in transit.
What should I do about MAL-2026-4598?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.