Supply chain · npm · High

Critical Malicious npm Package 'cma-self-hosted-sandbox-cf' Exfiltrates System Data

Threat Engine Auto-Feed · data current as of 2026-09-26

A malicious npm package, 'cma-self-hosted-sandbox-cf' version 1.0.0, automatically exfiltrates sensitive system information upon installation. This package is designed for credential/secret theft and reconnaissance, posing a critical supply-chain risk to any environment where it is installed.

  • Package: npm / cma-self-hosted-sandbox-cf
  • Affected versions: = 1.0.0
  • Severity: critical
  • Reach: ~0/wk
  • Exposure: 60/100 (High)

What happened — Credential / secret theft

The npm package 'cma-self-hosted-sandbox-cf' version 1.0.0 contains malicious code that executes automatically during installation. This code collects system identifiers and local account/host files, then exfiltrates this data to an attacker-controlled server.

How the attack works

This attack leverages a 'preinstall' hook within the package's `package.json` to execute an `index.js` script. This script gathers sensitive system information, including hostname, user details, home directory, DNS servers, and the contents of `/etc/passwd` and `/etc/hosts`. The collected data is then transmitted via HTTPS POST to a hardcoded, attacker-controlled domain. This is a form of dependency confusion or reconnaissance exfiltration, designed to steal credentials or secrets without user interaction.

Who's exposed

Profiles most at risk

  • Development teams using the npm ecosystem
  • CI/CD pipelines that pull unpinned or latest versions of npm packages
  • Organizations with internal package mirrors that may have ingested this malicious package

Conditions that increase exposure

  • Projects with unpinned dependencies that could inadvertently pull version 1.0.0 of 'cma-self-hosted-sandbox-cf'
  • Environments lacking robust package lockfiles (e.g., `package-lock.json`)
  • Build systems or developer machines where `npm install` is executed without strict package integrity checks

Blast-radius scenarios

  • An attacker gains reconnaissance data about the compromised system, including host identifiers and local user accounts.
  • The exfiltrated data could be used for further targeted attacks, such as privilege escalation or lateral movement within an organization's network.
  • Compromised credentials or system details could lead to unauthorized access to other systems or services.

What to do (defensive)

Detect

  • Scan `package.json` files for `cma-self-hosted-sandbox-cf` version 1.0.0.
  • Review network logs for outbound HTTPS connections to `49bl3t5yt786ymbtth24nnlbs2ytmka9.oastify.com`.
  • Monitor for unexpected file access to `/etc/passwd` or `/etc/hosts` by npm processes during installation.
  • Utilize software composition analysis (SCA) tools to identify known malicious packages in your dependencies.

Contain

  • Immediately remove `cma-self-hosted-sandbox-cf` version 1.0.0 from all `package.json` files and dependency trees.
  • Block network access to `49bl3t5yt786ymbtth24nnlbs2ytmka9.oastify.com` at the firewall or proxy level.
  • Isolate any systems identified as having installed the malicious package to prevent further data exfiltration or potential follow-on attacks.

Remediate

  • Audit all systems that installed `cma-self-hosted-sandbox-cf` version 1.0.0 for exfiltrated data and potential compromise.
  • Rotate all credentials and secrets that may have been present on affected systems.
  • Implement strict dependency pinning (e.g., using `package-lock.json` or exact version numbers) to prevent accidental installation of malicious versions.
  • Enhance CI/CD pipeline security to include automated vulnerability scanning and integrity checks for all pulled packages.

Frontier verdict — High

Prioritize immediate detection and removal of 'cma-self-hosted-sandbox-cf' due to critical data exfiltration risk upon installation.

Sources

For detection-engineering and awareness only · point-in-time · not security advice · sourced from the GitHub Advisory Database.