This threat involves a malicious npm package, @marketfront/commonecommerce version 7.0.0, published as part of a 25-package campaign under the @marketfront scope. The package uses a postinstall lifecycle hook to run a 162 KB obfuscated JavaScript payload that harvests a wide range of sensitive credential files and environment variables from the infected system. The harvested data is encrypted with RC4 and exfiltrated via two channels: an HTTPS POST to a dynamically assembled host and DNS-label tunneling designed to evade egress filtering. The package attempts to evade detection by inspecting runtime arguments and environment variables and delaying execution. It falsely claims to be a telemetry client for a legitimate organization, which does not exist. The actual library code is a stub, with the postinstall script being the only active malicious component. This campaign shares infrastructure and tooling with a previous campaign, indicating a persistent threat actor rotating npm scopes and maintainer identities. No official patch or remediation guidance is provided in the source data.

If installed, this package compromises the host by stealing a broad range of sensitive credentials and environment information, including SSH keys, cloud service credentials, Kubernetes and Docker configs, npm and git credentials, and shell history. This data exfiltration can lead to unauthorized access to cloud resources, source code repositories, and other critical infrastructure. The use of covert DNS tunneling alongside HTTPS exfiltration increases the likelihood of bypassing network security controls. The malicious code executes automatically at install time without user interaction, increasing the risk of widespread compromise in development environments that inadvertently install this package.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix or removal is published, users should avoid installing or updating to version 7.0.0 of @marketfront/commonecommerce. Audit existing environments for the presence of this package and remove it if found. Consider blocking the @marketfront npm scope in internal package registries and monitoring for suspicious postinstall scripts in dependencies. Due to the malicious nature of the package, no legitimate use is expected, so removal is the safest course of action.