Malicious code in tensorlake (npm)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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

Source: amazon-inspector (898b31edaabc82c76dc8d25f10ceee38c7ef51ee34887461a5bc8ce9f0378b50) The npm package tensorlake@0.5.144 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…

Published by the source

8 Oct 2026, 02:54 UTC

Last modified by the source

2 Nov 2026, 04:15 UTC

Source last checked

2 Nov 2026, 06:00 UTC

1. Revision 3 · amended · 2 Nov 2026

   Amended from osv record MAL-2026-17650

2. Revision 2 · amended · 31 Oct 2026

   Amended from osv record MAL-2026-17650

3. Revision 1 · created · 30 Oct 2026

   Published from osv record MAL-2026-17650

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-rqxj-g25x-4v9v

Advisory: Malicious code in tensorlake (npm)
IDs: GHSA-rqxj-g25x-4v9v
Record: https://patchnext.com/advisories/mal-2026-17650 (revision 3, source checked 2 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm tensorlake: affected >= 0.5.144, <= 0.5.144

## Suggested inspection (read-only)
- `npm ls tensorlake --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tensorlake.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/MAL-2026-17650 (OSV record MAL-2026-17650 lists affected ranges: npm tensorlake >=0)
- Verified: https://osv.dev/vulnerability/MAL-2026-17650 (OSV record MAL-2026-17650 lists affected ranges: npm tensorlake >=0.5.144 <=0.5.144)

Commands are suggestions: review each one before running it.