txs-sdk-libnpm

Package [email protected] could not be fully characterized: automated code tracing engaged with the package contents but the resulting output was withheld by the provider's safety filter, and no a static rule findings are recorded. The content-filter trigger on traced code is a signal often associated with malware-shaped material (credential theft, exfiltration, or remote code execution patterns), but without corroborating structural findings (hardcoded C2, credential-store reads, lifecycle-script fetch-and-execute, wallet enumeration, etc.) the specific behavior of this package cannot be described concretely from the available evidence. The package name suggests a generic SDK/library shape, which does not by itself indicate purpose or risk.

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.