registry  /  @marketfront/fashiononboardingpopup  /  7.0.0

@marketfront/fashiononboardingpopup@7.0.0

OSV Malicious Advisory

scanned 4h ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-6778 confirms this npm version as malicious. The @marketfront/fashiononboardingpopup package is part of a 25-package malicious campaign batch-published to the @marketfront npm scope by npm user 'marketfront' (marketfront@tutamail.com) 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.

Advisory
MAL-2026-6778
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @marketfront/fashiononboardingpopup (npm)
Details
The @marketfront/fashiononboardingpopup package is part of a 25-package malicious campaign batch-published to the @marketfront npm scope by npm user 'marketfront' (marketfront@tutamail.com) 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. --- ## Source: amazon-inspector (604b64d5bbde0068372b15b9af44e12d8a3ef9f6ab2cfee54f493d64d91fca8a) @marketfront/fashiononboardingpopup@7.0.0 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.
Decision reason
One or more suspicious static signals were detected.

Decision evidence

public snapshot
Behavioral surface
Source
DynamicRequireEnvironmentVars
Supply chain
MinifiedTrivial
Manifest
NoLicense
scanned 2 file(s), 159 KB of source

Source & flagged code

3 flagged · loading source
package.jsonView file
scripts.postinstall = node scripts/postinstall.js
High
Install Time Lifecycle Scripts

Package defines install-time lifecycle scripts.

package.jsonView on unpkg
scripts.postinstall = node scripts/postinstall.js
Medium
Ambiguous Install Lifecycle Script

Install-time lifecycle script is not statically allowlisted and needs review.

package.jsonView on unpkg
dist/index.jsView file
2// dist/index.js L3: module.exports = require('../src/index.js');
Medium
Dynamic Require

Package source references dynamic require/import behavior.

dist/index.jsView on unpkg · L2

Findings

1 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/index.js
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowNo License