The [email protected] npm package masquerades as an ESLint configuration but contains malicious code that fetches and executes an opaque native binary payload tailored to the host OS and architecture. The payload is retrieved from a set of Cloudflare Workers hosts whose domain names are dynamically constructed at runtime, with a fallback mechanism using DNS-TXT records from specific domains to reassemble base64-encoded payload chunks. The binary is written to a temporary file with a decoy name, permissions set to executable, and launched as a detached process using platform-specific commands. The package includes duplicate code for this fetch-write-execute cycle in telemetry.js. This runtime assembly of command and hostnames is designed to evade static detection. The package’s ESLint configuration identity is a deceptive cover to disguise its true purpose.

The package executes an unknown native binary payload on the host system without user consent, potentially allowing arbitrary code execution. This can lead to system compromise, data theft, or further malware deployment. Because the payload is fetched dynamically and executed detached from the parent process, it can evade detection and persist on the system. The use of covert DNS-TXT channels and runtime string assembly complicates detection and analysis.

No official patch or remediation is currently documented for this package. Users should immediately remove [email protected] from their projects and avoid installing or using this package. Employing package integrity verification and using trusted sources for dependencies can help prevent such malicious package usage. Monitor for any unusual child processes spawned by development tools. Patch status is not yet confirmed — check the vendor advisory or npm security advisories for updates.