Malicious code in nwfp-build-config (npm)

-= Per source details. Do not edit below this line.=-

Source: amazon-inspector (905a5825cb8abf7b385b98cfade02c315a4bc776bc37cfacd5ab20d5b8d03640)

On require() of nwfp-build-config, index.js loads lib/telemetry.js, which immediately runs an IIFE that reads the installer's hostname (os.hostname()) and username (os.userInfo().username), AES-256-CBC-encrypts the pair with a hardcoded 32-byte key, base32-encodes the ciphertext, splits it into DNS labels of up to 50 characters, and leaks the labels via dns.resolve4() queries to subdomains of cdn-assets.liderydigital.com, framed with start/end sentinel queries. The channel is a purpose-built covert DNS tunnel that bypasses HTTP egress controls; errors are swallowed in silent try/catch blocks. The destination is unrelated to the package's declared purpose of providing build configuration, and the 'telemetry' naming plus hardcoded encryption key are cover-story shaping around identity exfiltration.

Source: ghsa-malware (918305da861c018c4d00872a3fbd1d88902de80581628ba62e66eb1a098ebe56)

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.