Threat feed

leadstack-crm-connect-agent-backdoor

Unattributed publisher distributed a fake LeadStack CRM npm package that installs an AI agent backdoor as a root systemd service

Posted · Spectrum Delta Research Team

Summary

An unattributed publisher using the npm account zmaticoo distributed @leadstack/crm-connect, a fake LeadStack CRM client whose postinstall script installs the open-source Hermes Agent as a persistent backdoor on Linux servers. Nine malicious versions appeared on 16 November 2026; SafeDep flagged the package minutes after the last release and npm has removed it. Version 1.0.15 installs hermes-agent configured with Moonshot's Kimi model, fetches a .env and SOUL.md instructions from the attacker server at 72.62.1.108, and installs a Telegram gateway renamed leadstack-routing.service as a root systemd service; version 1.0.18 adds a user-level service with systemd linger when not root. Anyone the .env allows can chat commands to the agent, which can run shell commands, read and write files, browse, run code and schedule jobs. Later versions fetch JavaScript modules, a binary or an unpublished platform package and run them with the install process's full environment. SafeDep assesses the lures target CRM and broker-desk integration engineers, likely at forex and CFD brokerages; an 18 November lure advertised brandnet-connect to the same audience. No victim installation has been observed.

Breakdown

Targets

  • Industry: CRM and brokerage integration engineers

Technical exposure

  • Installs of @leadstack/crm-connect or brandnet-connect npm packages
  • Linux servers where npm install can create systemd services
  • CRM credentials and lead data on integration or staging hosts
  • Outbound Telegram long-polling and Moonshot API access allowed

Adversary

Unattributed · npm account zmaticoo, lookalike domain zmaticco.dev; no victim installation observed (B/2)

Procedures (3)

  1. Fake CRM package installs Hermes Agent as root service

    • T1543.002Create or Modify System Process: Systemd Service
    • T1105Ingress Tool Transfer

    Logs

    • npm and CI install logs · npm installs of @leadstack/crm-connect versions 1.0.15 through 1.1.1, @zmatdspcrm/trading-connector, @zmatdspcrm/brandnet-connect or brandnet-connect on staging or integration hosts, 16 to 18 November 2026
    • Linux systemd and process logs · systemd units leadstack-routing.service or leadstack-ingest-worker.service created by an npm postinstall script, described as LeadStack Lead Routing Daemon, configured to restart and start at boot; hermes-agent node processes running as root or with linger enabled

    Detectors

    • SafeDep malicious package analysis · Flagged @leadstack/crm-connect at 15:33 UTC on 16 November 2026, six minutes after the last version was published
  2. Telegram-gated agent executes chat commands on the server

    • T1059Command and Scripting Interpreter
    • T1071.001Application Layer Protocol: Web Protocols

    Logs

    • Web proxy and DNS logs · unexplained long-lived HTTPS long-polling connections to api.telegram.org and calls to api.moonshot.ai from integration or staging servers with no prior history of either destination
    • Linux process logs · node processes spawned by the leadstack service executing shell commands, reading and writing application files, or invoking browser tooling under the service account
  3. Later versions fetch and run remote payloads with full environment

    • T1105Ingress Tool Transfer
    • T1059Command and Scripting Interpreter

    Logs

    • EDR process and network events · npm postinstall processes downloading tarballs or binaries from zmaticco.dev, 72-62-1-108.sslip.io or 72.62.1.108 and executing them with the install process's inherited environment, including any CRM credentials

Indicators of compromise

IPs (1)

  • 72.62.1.108Attacker server used for bootstrap, agent configuration and payload downloads

Domains (5)

  • zmaticco.devLookalike domain registered 18 November 2026, resolves to the attacker server
  • 72-62-1-108.sslip.ioAlternate hostname for the attacker server used by version 1.0.20
  • api.leadstack.ioBundled fake CRM endpoint, does not resolve
  • api.telegram.orgAgent Telegram gateway command channel
  • api.moonshot.aiKimi model API called by the installed agent

URLs (2)

  • http://72.62.1.108:3000/api/v1/partner/bootstrapBootstrap URL bundled in version 1.0.15 configuration
  • https://zmaticco.dev/packages/brandnet-entitlement-1.0.0.tgzOptional dependency tarball declared by @zmatdspcrm/trading-connector 1.0.1

Hashes (6)

  • 29559f042f81c7a6cc642173eab09b0b02e369f47b594b68c78028ef2df10e4c@leadstack/crm-connect 1.0.15 tarball
  • 8cd56c6a036ae6d08cc07e64f98a3af7d836204d7620203bee5b8fd7d6931757@leadstack/crm-connect 1.0.18 tarball
  • 3083068c322829c9840f0931f7adfb39b8357d0d8a074d7f1967174631443154@leadstack/crm-connect 1.0.19 tarball
  • ce1812a6e1a5bc99cc705e44b10ae476324ea7930616508a11cc3173934e1abb@leadstack/crm-connect 1.0.20 tarball
  • d95fad3aea003d6b53645daa8d724ac32e4b2e25e6e4c71264fdb15b8b3adb@leadstack/crm-connect 1.0.21 tarball
  • 8a2f9a526955a07b183c3f3658d2088eb4c8c66d3fcaf8fb91322944b82e6e92@leadstack/crm-connect 1.0.29 tarball

Sources

Grades are source reliability (A–F) and information credibility (1–6).

Questions, detections or sightings of leadstack-crm-connect-agent-backdoor? Bring them to the community.