MalwarePublished 2 Jul 2026Updated 6 Jul 2026

@marketfront/madvpopup (npm) · Malicious Code

Affects @marketfront/madvpopupSource GCVE Database

Malicious package : remove @marketfront/madvpopup and rotate any secrets on hosts that installed it.

Data as of 6 Jul 2026, 23:22 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6785

What to do

Remove @marketfront/madvpopup from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@marketfront/madvpopup	Affected =7.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The @marketfront/madvpopup npm package version 7.0.0 is part of a malicious campaign involving 25 packages published within a short time frame. It contains a heavily obfuscated postinstall script that executes automatically during npm install, harvesting sensitive credential files and environment variables from the host system. The stolen data is exfiltrated via encrypted HTTPS requests to a concealed command-and-control server. The package masquerades as a legitimate e-commerce frontend component and uses an internal-corporate namespace style to facilitate dependency confusion attacks against targeted organizations.

Impact

Systems that install @marketfront/madvpopup version 7.0.0 are at risk of having sensitive credentials and environment information stolen, including SSH keys, cloud service credentials, container and Kubernetes configurations, and other secrets. This can lead to unauthorized access to cloud resources, source code repositories, databases, and other critical infrastructure. The attack targets developer machines and CI environments, increasing the risk of widespread compromise within affected organizations.

Defensive guidance

The package should be considered malicious and immediately removed from any projects or dependency trees. Organizations should audit their npm dependencies for packages published under the @marketfront scope and specifically version 7.0.0 of @marketfront/madvpopup. Developers should avoid installing packages from untrusted or suspicious namespaces and verify package provenance. Use of internal npm registries with strict access controls and dependency allowlists can help prevent dependency confusion attacks. Monitor for any signs of credential compromise and rotate affected credentials if exposure is suspected.

Summary

This threat involves the @marketfront/madvpopup npm package version 7.0.0, which includes a postinstall hook executing a 162KB obfuscated payload. The payload harvests approximately 20 sensitive credential files (including SSH keys, AWS credentials, Kubernetes configs, Docker configs, npm and git credentials, environment files, and bash history) and collects extensive environment and system metadata. The harvested data is compressed and exfiltrated over HTTPS with custom headers to an obfuscated remote endpoint, with additional DNS beaconing. The campaign shares tooling and infrastructure with a previous malicious campaign (@emcd-vue), indicating a persistent threat actor using rotating npm scopes and disposable maintainer emails. The package's code is non-functional beyond the postinstall script, which is designed to deceive via corporate namespace impersonation and dependency confusion.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 6 Jul 2026, 23:22 UTC

Technical details

References

Community reviews