취약점

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

Source: amazon-inspector (5e3ff057a42800ad78024ac1c48e0d6fbf9c828eb828a41e6737c32b6174ce8c)

Package is published publicly on npm at version 100.20.33 — a version-number shape used in dependency-confusion attacks to outrank private internal packages of the same name. The package.json claims authorship by 'Atlassian Ecosystem Engineering' and describes itself as an 'Atlassian internal demonstration and utility framework', but the package is published to the public registry under no Atlassian-owned scope. The main entry index.js contains only try { require('nw-demo-utils'); } catch (e) { } — its sole behavior on import is to silently load and execute a separately-published transitive dependency (nw-demo-utils ^1.0.16), with errors swallowed to hide failures. The README instructs consumers to require('nw-demo'), which transitively executes nw-demo-utils' module-load code in the installer's process. The wrapper itself ships no payload; it functions as a loader that laundries arbitrary code from nw-demo-utils into any pipeline that mistakenly resolves the public package over a private internal one.

Source: ghsa-malware (a8b0000bbe860e0be3251c1f9d4909f0f7c7f752e64fd9f49c9f728efac5c633)

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.