---
title: A malicious npm package installed a real AI agent as its backdoor: @leadstack/crm-connect set up Hermes Agent as a root systemd service, pulled its persona from the attacker's server and handed it to a Telegram bot | ctxsec
url: https://ctxsec.com/items/malicious-npm-leadstack-crm-connect-installs-hermes-agent-as-root-systemd-service-tasked-over-telegram-soul-md-from-attacker-server
description: "SafeDep says npm user 'zmaticoo' published nine versions of @leadstack/crm-connect, posing as the official client for a 'LeadStack' CRM, on Nov 16. Its postinstall script installed the open-source Hermes Agent, downloaded the agent's .env (keys) and SOUL.md (standing instructions) from 72.62.1.108, connected it to the attacker's Telegram bot and registered it as 'leadstack-routing.service'. Run as root, that gave the attacker shell, file, browser and scheduling control of the server from a chat. Later versions swapped the agent for downloaded JavaScript or a binary. npm removed the package, but on Nov 18 the same publisher put up @zmatdspcrm/trading-connector, @zmatdspcrm/brandnet-connect and brandnet-connect, which have no code of their own and pull a dependency from zmaticco.dev, so the payload can change at any time. Lures point at forex/CFD brokerage CRM integrators."
status: "research (SafeDep analysis, Nov 19, 2026); npm removed @leadstack/crm-connect; follow-on packages were still live on Nov 19"
published: 2026-11-19
---

> SafeDep says npm user 'zmaticoo' published nine versions of @leadstack/crm-connect, posing as the official client for a 'LeadStack' CRM, on Nov 16. Its postinstall script installed the open-source Hermes Agent, downloaded the agent's .env (keys) and SOUL.md (standing instructions) from 72.62.1.108, connected it to the attacker's Telegram bot and registered it as 'leadstack-routing.service'. Run as root, that gave the attacker shell, file, browser and scheduling control of the server from a chat. Later versions swapped the agent for downloaded JavaScript or a binary. npm removed the package, but on Nov 18 the same publisher put up @zmatdspcrm/trading-connector, @zmatdspcrm/brandnet-connect and brandnet-connect, which have no code of their own and pull a dependency from zmaticco.dev, so the payload can change at any time. Lures point at forex/CFD brokerage CRM integrators.

[← Context & Harness Attacks](/context) · [markdown](/items/malicious-npm-leadstack-crm-connect-installs-hermes-agent-as-root-systemd-service-tasked-over-telegram-soul-md-from-attacker-server.md)

research (SafeDep analysis, Nov 19, 2026); npm removed @leadstack/crm-connect; follow-on packages were still live on Nov 19

2026-11-19 · published here

2026-11-21 11:44 AM ET

### A malicious npm package installed a real AI agent as its backdoor: @leadstack/crm-connect set up Hermes Agent as a root systemd service, pulled its persona from the attacker's server and handed it to a Telegram bot

- **Why it matters:** the attacker didn't write an implant; a general-purpose agent with tools is one. Its behaviour is set by a SOUL.md that can be swapped server-side without a new npm release. Hermes's prompt-injection scanner only warns about that file and loads it anyway.
- See the hunt and the tip below.

Sources: [SafeDep: Malicious npm Package Turns Hermes Agent into a Backdoor (Nov 19, 2026)](https://safedep.io/blog/malicious-npm-leadstack-crm-connect-hermes-agent-backdoor) · [Corgea: @leadstack/crm-connect on npm installed Hermes Agent as a root systemd service (Nov 2026)](https://corgea.com/research/leadstack-crm-connect-npm-hermes-agent-telegram-backdoor-november-2026)
