config-normalizer-node@1.0.0
Malicious code in config-normalizer-node (npm)
Analysis
This package runs a postinstall hook (scripts/install.js) that contacts an undisclosed remote endpoint before the install completes. The destination is never written in plain text: lib/beacon.js assembles it at runtime from single-fragment array entries — 'htt', 'ps', '://', 'my-contolled-backend', '/beacon' — producing hxxps://my-contolled-backend/beacon, and issues a plain GET to it while printing "[signal] install ok" to the console. The hostname is split apart specifically to keep it out of simple string matching, is a misspelled lookalike ("contolled") of "controlled", and is not the package's repository, registry or documentation host — neither package.json nor the README names it. The endpoint's purpose is stated only in a postinstall source comment and the README, which describe it as an empty install-completion diagnostics ping; the shipped GET carries no query string, path parameters, headers or body, and the shipped code reads no local files, environment values or credential files and spawns no processes. The observable effect is therefore a covert install-time beacon reporting that the package was installed to a non-standard host. The rest of the package is ordinary recursive configuration-merge logic in index.js.
- analyzed by
- Leitwacht
- first seen
- Nov 4, 2026, 03:35 AM
- analyzed
- Nov 4, 2026, 03:38 AM
Related advisories
- persona-ai-sdk@1.0.0
- botmaker-cli@0.1.19
- n8n-nodes-flowstats@1.0.0
- chai-logger@3.0.2
- lufxchwmxwyps@1.0.0
- farplotzy@0.1.0
- ausitool@1.0.1
- strapi-plugin-feedmeeb@3.6.8
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.