field-plus

Details

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

## Source: amazon-inspector (0112dc4801bb261e86a2f68d5fd49b6c955bb4e82f872c72e61e49cc638ca91c)
package.json declares both preinstall and postinstall scripts that run curl against a hardcoded bare-IP HTTP endpoint (http://3.7.226.146:9000/callback), sending the installer's username ($(whoami)), hostname ($(hostname)), current working directory ($(pwd)), and a timestamp as query-string parameters. Output is suppressed and errors swallowed with `|| true` so the beacon stays silent during `npm install`. The tarball ships only package.json — `main: index.js` is declared but not present — so the package has no library functionality; its sole effect on installation is the identity beacon. Version 99.99.1 plus the description "testing field plus" is the canonical shape of a dependency-confusion / namespace-squat probe used to identify which organizations resolve an internal-named package from the public registry.

## Source: ghsa-malware (b9c01dfacc7ff1df16b13ba67ffe0c3ac7ff2e533c1d44bd3d402736814f3656)
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 (2)

• 99.99.1
• 99.99.2

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