@redman89405/my-module

Details

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

## Source: amazon-inspector (ee7d38498dcd2e2a3afc4ed3b3a5136cb88e11693ef59fc7676bf35cd89b932c)
The package ships `code.png` alongside `index.js` and exports a function `imageToCode` that reads a length-prefixed byte stream from the first pixel row of the PNG and passes the decoded string to `Function(...)()`, an eval-equivalent sink. The executable content is hidden inside an image asset rather than present as readable source, so the code that will run cannot be seen by inspecting the npm tarball. The API is exported alongside trivial `hello`/`add` helpers with no documented purpose for image-based code loading, and the author retains the ability to change the payload in future publishes without any visible source diff. The code path relies on browser-only globals (Image, canvas) so it does not fire on Node `require`; harm requires a consumer application to call `imageToCode` in a browser context, at which point arbitrary author-supplied JavaScript executes in that page.

## Source: ghsa-malware (58f8e0d965e65d298a38295487ebe0c363ea7da343649827903915cc655f3730)
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)

• 1.0.0
• 1.1.0

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