The [email protected] npm package exhibits a canonical dependency confusion attack pattern by using an internal-sounding name and an artificially high version number to supersede legitimate packages. Its index.js exports an empty object, providing no functionality, but it declares a dependency on a tarball hosted outside the npm registry at a Google Cloud Storage URL containing the path segment 'depenconf', explicitly indicating dependency confusion. Installing this package causes npm to fetch and install the off-registry tarball, which may contain lifecycle scripts that execute on the installer's machine, allowing arbitrary code execution. The tarball contents are mutable by whoever controls the bucket, enabling ongoing malicious activity. The package is considered fully compromising any system where it is installed.

Installing [email protected] results in arbitrary code execution on the installer's machine due to lifecycle scripts in an off-registry tarball. This leads to full system compromise, including potential unauthorized access to secrets and keys stored on the system. The compromise is severe enough that simply removing the package does not guarantee remediation, as attackers may have established persistent control.

No official patch or fix is available for this malicious package. The recommended mitigation is to immediately remove the [email protected] package from affected systems. All secrets and keys stored on compromised machines must be rotated from a separate, trusted system. Due to the high risk of persistent compromise, consider rebuilding or thoroughly cleaning affected systems. Avoid installing packages from untrusted or suspicious sources and verify package provenance before installation.