@leadstack/crm-connect
This report shows the evidence for @leadstack/crm-connect@1.0.29. 7 of 8 known versions are blocked or flagged. The newest version, 1.1.1, is allowed.
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-20330 confirms this npm version as malicious.
Advisory
MAL-2026-20330
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @leadstack/crm-connect (npm)
Details
Package advertises itself as a 'LeadStack CRM' Node.js connector for lead ingest and routing, but its postinstall script performs a coordinated backdoor deployment on the installer's host. The script fetches configuration from a hardcoded bare-IP endpoint over plain HTTP (http://72.62.1.108:3000/api/v1/partner/bootstrap), writes the returned env_lines and a SOUL.md profile into a hidden ~/.leadstack directory, then creates ~/.leadstack/runtime and runs `npm install --ignore-engines hermes-agent@0.22.7` into it — pulling an unrelated agent package into a concealed runtime directory. It then invokes `hermes-npm setup` and `hermes setup gateway --install --system --run-as-user root --no-start-now`, installing a boot-persistent root-privileged systemd unit. The unit file is copied to /etc/systemd/system/leadstack-routing.service with `Hermes Agent Gateway` strings rewritten to `LeadStack routing`, and the original unit is disabled and deleted — deliberate concealment of the persistence artifact's origin. The service is then enabled and started, and the script waits for a Telegram polling-mode channel to come up, configuring an LLM model provider (kimi-coding). The resulting daemon runs as root on every boot and takes commands from a remote Telegram channel, giving the operator of 72.62.1.108 and the Telegram bot full remote code execution on the installer's host. The configuration source (bare-IP, plain HTTP, unpinned content) means the C2 operator controls what the daemon runs on every installer. The CRM connector framing in package.json and README does not match any of this behavior.
## Source: ghsa-malware (327afd7445e5c86dc514045f8da08de4e7d1abef1b5427dc14d7ea4d0221e0bc) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.