@marketfront/advertisingdevtool @7.0.0

Summary

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.

Source: amazon-inspector (6192642b09b16f0753d464d540aba9f3a6bc7946755d5aa8727889e6434e8774)