Which versions of @marketfront/footer are malicious?

The following npm versions of @marketfront/footer are flagged malicious: 7.0.0. Treat any of these as compromised.

How do I remediate @marketfront/footer if I installed it?

@marketfront/footer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @marketfront/footer — how do I know if it already compromised me?

If @marketfront/footer was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @marketfront/footer part of a known attack campaign?

Yes — @marketfront/footer is associated with the IN-MAL-2026-008028 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @marketfront/footer across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @marketfront/footer (version 7.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @marketfront/footer across your stack and pipelines.

Malicious package

@marketfront/footernpm

@marketfront/footer is a confirmed malicious npm package (MAL-2026-6780) that steals credentials and exfiltrates sensitive data (malicious version 7.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @marketfront/footer (npm)

MAL-2026-6780

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @marketfront/footer

What this malware does

The @marketfront/footer package is part of a 25-package malicious campaign batch-published to the @marketfront npm scope by npm user 'marketfront' ([email protected]) within a roughly 3-minute window on 2026-07-01. All packages in the campaign were published at version 7.0.0 and use e-commerce/marketing frontend component names as cover.

The package declares a postinstall hook (node scripts/postinstall.js) that executes heavily obfuscated (obfuscator.io-style) code automatically at npm install time. Static analysis of the decoded payload revealed a credential harvester that dynamically requires fs, os, http, https, zlib, path and dns, then reads approximately 20 sensitive credential files including ~/.ssh, ~/.aws/credentials, ~/.kube/config, ~/.docker/config.json, ~/.npmrc, ~/.netrc, ~/.pgpass, ~/.git-credentials, ~/.env and ~/.bash_history. Collected data is exfiltrated via a gzip-compressed HTTPS POST with a custom X-Secret header to the path /api/v1/events, alongside a DNS resolver beacon. The command-and-control host is concealed behind an additional RC4+XOR encryption layer around an embedded configuration blob and was not statically resolved.

The decoded behavioral payload (module requires, credential-file target list, exfiltration headers and endpoint) is byte-for-byte identical across sampled packages in the campaign. The campaign shares tooling and infrastructure patterns (obfuscated postinstall credential harvester, X-Secret header, /api/v1/events exfiltration path, RC4-concealed C2) with the earlier @emcd-vue campaign, indicating the same actor rotating scopes and disposable maintainer emails.

On npm install, scripts/postinstall.js — a 160KB obfuscator.io-style bundle with an RC4-decoded string array and runtime-assembled identifiers — collects installer-side secrets and host identity and tunnels them out over DNS to an attacker-controlled resolver. Data collection covers the entirety of process.env (bulk CI/build secrets such as AWS_*, GITHUB_TOKEN, NPM_TOKEN, database credentials), host identifiers from os.userInfo()/os.hostname()/os.networkInterfaces(), Windows environment variables (USERDOMAIN, COMPUTERNAME, APPDATA, LOCALAPPDATA, TEMP, PROGRAMDATA, PROCESSOR_ARCHITECTURE), and the contents of well-known home-directory secret files including ~/.aws, ~/.ssh, ~/.npmrc, ~/.docker, ~/.gitconfig, ~/.netrc, and browser/shell profile paths. The harvested payload is JSON-serialized, gzipped via zlib.gzipSync, XOR-keyed, base32-encoded, split into 50-character chunks, and each chunk is emitted as a DNS TXT query of the form <seq>.<total>.<idx>.<rand>.<subdomain>.<attacker-host> using a dns.Resolver's resolveTxt — a channel specifically chosen to bypass HTTP egress filtering common on CI/build networks. The package's declared purpose ("internal database utilities with connection pooling, query builder and migration support") is a cover story: main points at dist/index.js, which only re-exports an absent src/index.js, so the tarball ships no functional library code — only the obfuscated postinstall. The @marketfront scope and marketfront.io publisher metadata additionally have the shape of an internal-name impersonation targeting a specific organization (dependency-confusion pattern).

Malicious versions

1 flagged

7.0.0

Indicators of compromise (SHA-256)

df4b30bc8f0ba99a70d152a0b6aa01a9acc3605505c3c3c31c8c03cc5ea4a639

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @marketfront/footer (version 7.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @marketfront/footer across your stack and pipelines.
If you installed it — respond
@marketfront/footer is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @marketfront/footer was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @marketfront/footer before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @marketfront/footer on npm has been identified as a malicious package (version 7.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008028

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @marketfront/footer-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database