Which versions of @marketfront/blenderdevtool are malicious?

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

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

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

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

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

Malicious package

@marketfront/blenderdevtoolnpm

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

MAL-2026-6768

Immediate action

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

npm uninstall @marketfront/blenderdevtool

What this malware does

The @marketfront/blenderdevtool 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 executes an obfuscator.io-style bundle (212-entry RC4-decoded rotated string array, integer opaque predicates, char-code array constructors) that reads installer-owned secret files including ~/.npmrc, ~/.aws/credentials, ~/.ssh/, ~/.docker/config.json and.env, bulk-scrapes process.env, and collects host identifiers (os.hostname, os.userInfo, network interfaces). The collected payload is XOR-encrypted with a key derived from the package identity, chunked into a 33-character alphabet, and exfiltrated as recursive DNS queries via dns.Resolver().resolve to a hardcoded external host — a channel chosen to bypass HTTP egress filtering and proxy allowlists. The install path is gated by an anti-analysis check that scans process.argv and NODE_OPTIONS for instrumentation fingerprints and runs a CPU-timing loop to detect VMs/debuggers, so sandboxed installs appear inert. The package additionally exhibits a dependency-confusion shape: it uses the @marketfront/ scope, its README labels it an 'Internal package — Platform Engineering Team', and its metadata (homepage/repository/bugs) points at *.marketfront.io hosts, indicating the public-registry publish is intended to be resolved in place of an internal package of the same name by a target organization's build pipeline. The README claim of 'anonymous telemetry' is a cover story that does not match the observed behavior.

Malicious versions

1 flagged

7.0.0

Indicators of compromise (SHA-256)

cbaf34bd1bf73af787679197a51e9147f20a2f1ade5576e4b8ca9d9a36cf7363

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

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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