Which versions of @marketfront/advertisingdevtool are malicious?

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

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

@marketfront/advertisingdevtool 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/advertisingdevtool — how do I know if it already compromised me?

If @marketfront/advertisingdevtool 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/advertisingdevtool part of a known attack campaign?

Yes — @marketfront/advertisingdevtool is associated with the IN-MAL-2026-008018 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/advertisingdevtool 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/advertisingdevtool (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/advertisingdevtool across your stack and pipelines.

Malicious package

@marketfront/advertisingdevtoolnpm

@marketfront/advertisingdevtool is a confirmed malicious npm package (MAL-2026-6764) 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/advertisingdevtool (npm)

MAL-2026-6764

Immediate action

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

npm uninstall @marketfront/advertisingdevtool

What this malware does

The @marketfront/advertisingdevtool 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.

The package declares postinstall: node scripts/postinstall.js and ships a 166KB obfuscator.io-style bundle (string-array, RC4-decoded literals) that runs automatically on npm install. On execution it (1) collects host reconnaissance — OS hostname/arch/platform/type/release/version, os.userInfo(), CPU info, network interfaces, npm_config_user_agent, and Windows-specific USERDOMAIN, COMPUTERNAME, PROCESSOR_ARCHITECTURE, APPDATA, LOCALAPPDATA, TEMP, PROGRAMDATA — and dumps process.env in full (CI tokens, AWS_*, GITHUB_TOKEN, and similar secrets); (2) scans the user's home directory (paths derived from os.homedir() including.aws,.ssh,.npmrc,.config, and browser profile directories) via fs.readdirSync + fs.readFileSync and packs their contents into the payload; (3) encrypts the payload and exfiltrates over two parallel channels — DNS-tunnel using dns.Resolver.resolve4() with base32-encoded XOR/RC4-encrypted chunks embedded as subdomain labels (bypasses HTTP egress filtering) and an HTTPS POST fallback with the same encrypted body; and (4) gates the entire payload behind an anti-analysis IIFE that inspects process.execArgv and process.env.NODE_OPTIONS for --inspect/--inspect-brk and runs a wall-clock timing loop to detect debugging, aborting on non-clean hosts. The package presents itself as an 'Internal configuration loader with env, vault and remote config support' and points at nonexistent internal infrastructure (github.marketfront.io, npm.marketfront.io, jira.marketfront.io) — the classic dependency-confusion cover story targeting organizations that may have a private @marketfront scope.

Malicious versions

1 flagged

7.0.0

Indicators of compromise (SHA-256)

6192642b09b16f0753d464d540aba9f3a6bc7946755d5aa8727889e6434e8774

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/advertisingdevtool (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/advertisingdevtool across your stack and pipelines.
If you installed it — respond
@marketfront/advertisingdevtool 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/advertisingdevtool 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/advertisingdevtool 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/advertisingdevtool 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-008018

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @marketfront/advertisingdevtool-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