Which versions of @marketfront/navbar are malicious?

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

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

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

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

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

Malicious package

@marketfront/navbarnpm

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

MAL-2026-6787

Immediate action

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

npm uninstall @marketfront/navbar

What this malware does

The @marketfront/navbar 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 registers scripts/postinstall.js as an npm postinstall hook. The script is heavily obfuscated (obfuscator.io-style string-array with RC4 decoder, hex-named functions, runtime string decoding) and, on npm install, harvests a full profile of the installing machine: os.hostname(), os.userInfo().username, os.homedir(), os.platform(), os.arch(), os.networkInterfaces(), process.argv0, process.cwd(), the complete process.env, npm_config_user_agent, and Windows-specific USERDOMAIN, COMPUTERNAME, APPDATA, LOCALAPPDATA, TEMP, and PROGRAMDATA, along with the package name and version. The collected data is JSON-serialized, zlib-compressed, XOR-encrypted, and exfiltrated over two channels to a runtime-decoded remote host: an HTTPS POST and a DNS TXT tunnel that chunks the payload into subdomain labels via a custom dns.Resolver with attacker-specified servers. Payload execution is gated by anti-analysis checks — inspection of process.argv and NODE_OPTIONS for 'node_modules' / '.npm' tokens, a Date.now() timing threshold, and a global sentinel for single execution — designed to fire on real developer and CI installs while staying silent under scanners. The package presents itself as an 'Internal structured logger' under the name @marketfront/navbar, but has no working library surface: dist/index.js re-exports../src/index.js, which is not shipped in the tarball. The entire functional behavior is the install-time stealer. Developer and CI process environments routinely contain cloud provider tokens, npm publish tokens, registry credentials, and CI secrets, so the impact is credential compromise of the installer's account/infrastructure.

Malicious versions

1 flagged

7.0.0

Indicators of compromise (SHA-256)

2a0a9490d91761fdf242bf7e3b9a97cc4f0df29f1306d7e476dad08aad25c17a

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

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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