Malicious code in @drone-js-ext/core (npm)

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

Source: amazon-inspector (9173b1e0c1d01cafb58dfbcad8b59a50f49700cc911e22df2787f5a92b4c6e43)

The package ships a beacon.cjs that collects host identifiers (hostname, install path, current working directory, Node version) and POSTs them in cleartext to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. This beacon is wired to run automatically in two places: package.json declares scripts.postinstall = "node beacon.cjs", so it executes on npm install, and index.js also invokes the same fire() function at module load, so it executes again on require(). The remainder of the package is a no-op Proxy shim with no functional code matching the stated Compatibility shim description. The scope-and-version shape (@drone-js-ext/core at version 99.0.1 against a plausibly internal @drone-js-ext/* namespace) matches a dependency-confusion lure designed to be resolved in place of a private internal package. A README self-label of dependency-confusion test does not change the behavior: any installer that resolves this package has host-identifying data sent to a non-vendor, non-registry, bare-IP, plaintext-HTTP collector controlled by a third party.

Source: ghsa-malware (338c919fc73c66cb9bd18fa251359467039387724d1f8f41e6d3bb88f52ddc6f)

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.