The sams-sr-sdk-h5 package was published to the npm registry by an attacker as part of a dependency confusion campaign targeting organizations using an internal 'sams' namespace. The package declares a preinstall hook that runs automatically upon installation, which executes a script that collects the installing host's public IP address and other personally identifiable information (PII) such as hostname, OS username, and runtime metadata. This information is sent to a hardcoded attacker-controlled Sentry DSN with sendDefaultPii enabled. Additionally, the package's initialization silently forwards application errors and PII to the attacker's Sentry project if no DSN is supplied by the user, further compromising privacy and security. The package name and minimal README are crafted to mimic legitimate internal packages, increasing the likelihood of accidental installation. The malicious payload is identical across packages published by this attacker, differing only in package name and target Sentry project. The affected version is exactly 7.0.0. No patch or official fix is currently documented.

Installing this package results in automatic exfiltration of sensitive host metadata including public IP address, hostname, OS username, and runtime environment details to an attacker-controlled Sentry project. Additionally, any application errors and end-user PII may be silently sent to the attacker if the package is used without specifying a different Sentry DSN. This compromises confidentiality and privacy of the host and potentially end users. The presence of this package on a system indicates a high likelihood of compromise, and all secrets and keys on the affected system should be considered exposed and rotated. The package enables attacker reconnaissance and data leakage without user interaction beyond installation.

No official patch or remediation is currently available. Users should immediately remove the sams-sr-sdk-h5 package version 7.0.0 if installed. Because the package executes code at install time that exfiltrates sensitive data, any system with this package installed should be considered fully compromised. It is strongly recommended to rotate all secrets and keys stored on the affected system from a separate, trusted environment. Avoid installing packages from untrusted or unknown sources, especially those mimicking internal namespaces. Monitor for and block suspicious packages in your supply chain. Check vendor advisories or trusted security sources for updates on remediation or detection tools.