Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @marketfront published 25 malicious packages. See the full campaign →
Malicious package

@marketfront/fashiononboardingpopupnpm

Advisory published Updated

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

MAL-2026-6778
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @marketfront/fashiononboardingpopup

What this malware does

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

@marketfront/[email protected] declares "postinstall": "node scripts/postinstall.js" which auto-executes during npm install. scripts/postinstall.js is a heavily obfuscated payload (obfuscator.io-style hex string array, base64+RC4 string decoder) whose decoded behavior collects host identity (os.hostname, os.userInfo, os.networkInterfaces, os.cpus, platform, arch), Windows environment variables (USERDOMAIN, COMPUTERNAME, APPDATA, LOCALAPPDATA, TEMP, PROGRAMDATA), process.argv, process.cwd(), and the entire process.env, RC4-encrypts the JSON, and POSTs it via require('https'|'http').request to a hardcoded remote endpoint the installer never opted into. The script also contains anti-analysis logic that inspects process.argv and NODE_OPTIONS for debugger flags and applies a timing check, disabling execution when analysis is suspected. The package's advertised library surface is a stub: dist/index.js re-exports ../src/index.js, which is not shipped in the tarball; the package's main provides no real functionality. Metadata (description "Internal structured logger", repository github.marketfront.io, homepage docs.marketfront.io) is styled to imitate an internal private package on public npm — a dependency-confusion social-engineering layer paired with the working install-time exfiltration payload.

Malicious versions

1 flagged
7.0.0

Indicators of compromise (SHA-256)

604b64d5bbde0068372b15b9af44e12d8a3ef9f6ab2cfee54f493d64d91fca8a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @marketfront/fashiononboardingpopup (version 7.0.0).

  2. If you installed it — respond

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

  3. Did it already run?

    If @marketfront/fashiononboardingpopup was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @marketfront/fashiononboardingpopup 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-008026

References

Credits

  • Amazon Inspector · finder
  • SafeDep · finder

Detect & block this

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

Explore

@marketfront/fashiononboardingpopup (npm) malicious package — MAL-2026-6778 | O3 Security