Skip to content

advisory-catalog: tensorlake-2026-10-08 - #83

Merged
thom-pplx merged 1 commit into
perplexityai:mainfrom
ronheichman:advisory-catalog/tensorlake-2026-10-08
Oct 8, 2026
Merged

thom-pplx merged 1 commit into
perplexityai:mainfrom
ronheichman:advisory-catalog/tensorlake-2026-10-08

Conversation

@ronheichman

Copy link
Copy Markdown
Collaborator

Source: https://socket.dev/blog/tensorlake-compromise (Socket, published 2026-10-08T02:54:50Z)

Affected: npm tensorlake@0.5.144 (published 2026-10-08T01:12:07Z; Socket flagged at 01:23:10Z).

Non-origin corroborators:

  • OSV MAL-2026-17650, published 2026-10-08T02:54:39Z, lists 0.5.144 (also carries an introduced: 0 range).
  • GitHub Advisory Database GHSA-rqxj-g25x-4v9v, published 2026-10-08T02:54:39Z, tensorlake = 0.5.144 (also a >= 0 range).
  • npm registry packument: time["0.5.144"] = 2026-10-08T01:12:07.320Z.

Yank observation: the npm packument keeps the 0.5.144 publication timestamp but no longer has a versions["0.5.144"] entry or tarball; dist-tag latest is 0.5.143. deps.dev returns "version not found". This is consistent with the release being removed by npm.

Scope note: OSV/GHSA also carry all-versions ranges (standard for malware advisories). This catalog lists only 0.5.144, the version Socket and both advisories enumerate.

Dropped: none (1/1 package-version claim cataloged).

Files: threat_intel/tensorlake-2026-10-08.json (new; validated against docs/schema/v0.2.0/exposure-catalog.schema.json) and one threat_intel/README.md row.

@ronheichman
ronheichman marked this pull request as ready for review October 8, 2026 14:16
@thom-pplx
thom-pplx merged commit c1e83c0 into perplexityai:main Oct 8, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants