Malicious code in tensorlake (npm)

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

Source: amazon-inspector (898b31edaabc82c76dc8d25f10ceee38c7ef51ee34887461a5bc8ce9f0378b50)

The npm package [email protected] ships lib/setup.mjs as a heavily obfuscated single-line script using hex-mangled identifiers (_0x15c964, _0x35672e,...), a transformation shape typical of hostile loader code rather than ordinary minification. Multiple shipped bundles under dist/ (dist/index.cjs, dist/applications/index.cjs, dist/sandbox-image.cjs, dist/function-agent/main.cjs, dist/function-executor/main.cjs, and their.js counterparts) combine require("child_process") with repeated POST request primitives and shell utilities such as curl and ping, including host/id-collection patterns alongside outbound HTTP calls. Automated contextual tracing of these files was blocked by the provider safety filter after the model engaged with the content, which is a pattern that correlates with hostile code rather than benign SDK traffic. The combination of an obfuscated setup script and child_process + hardcoded HTTP POST patterns in the shipped bundles is consistent with install-time or load-time execution of attacker-controlled behavior against the installer's host.

Source: ghsa-malware (de1a505f248f0041777b65937111dd0448f6a5e84fa4e3b95a0a00cb21b7589c)

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.