Threats Tagged 'mal-2025-5016'

The package communicates with a domain associated with malicious activity. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3d282025fb2ec1b4012e3b979cec1f66520e643fcadfd2864e54989de50dd00d) The package.json preinstall script runs `wget` against an attacker-controlled webhook.site URL, passing `$(whoami)`, `$(pwd)`, and `$(hostname)` as query parameters, executing automatically on `npm install`. This matches the npm-lifecycle-external-fetch and credential/telemetry exfiltration patterns (findings a static pattern match, a static pattern match, a static pattern match, a static pattern match, a static pattern match). the analysis confirms contextually that the script performs reconnaissance exfiltration to a non-registry collector, and config.unsafe-perm is set to ensure execution. the analysis further notes that the declared main entrypoint is missing and the tarball contains only package.json — the package exists solely to trigger the beacon, with no legitimate runtime functionality. Self-identification as a 'PoC' does not change the risk to an unintended installer (e.g., via dependency confusion). ## Source: ghsa-malware (66a5014b00cbe1f0b68f513878acb21a0801758710524c715d837ef999ad3752) 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.