Tensorlake

How they got in, as reported. A supplier or vendor that was compromised first.

← All cases
Date
8 Oct 2026
Place
United States
Who
Tensorlake
The way in
Vendor compromise
Source
The Hacker News
01 · What was reported

What was reported.

Tensorlake's official npm package was compromised to distribute malware as part of the ChainDrop and Shai-Hulud supply chain attack campaign. Malicious commits made under a maintainer's name introduced credential-stealing and self-propagating code into version 0.5.144 of the SDK.

The way in the source reports: a supplier or vendor that was compromised first.

According to StepSecurity, the malicious files were pushed to the main branch of tensorlakeai/tensorlake under a maintainer's name, after which the package was released from that same repository.The Hacker News, added to these pages on 8 Oct 2026. The source
02 · The way in

What a vendor compromise is.

A vendor compromise starts at a supplier. An attacker gets into a provider first and reaches its customers through the access or the trust the provider already has.

A message from a real supplier's real mailbox asking to change bank details is the common form. Software updated by a provider the attacker controls is another.

We read a supplier's own public mail records: whether forged mail in its name would be refused and whether look-alikes of its name are registered.

A reading of public records cannot see inside the supplier's systems. A changed bank detail is confirmed by a call to a number already on file, never by a reply.

This part is true of every case of this kind. It says nothing more about Tensorlake than the source does.

03 · What we check for it

What we check for it.

The outside services your domain depends on.

04 · If this happens at your firm

If this happens at your firm.

  • Confirm every change of bank details on a number you already hold, even inside a real email thread.
  • Agree with your main suppliers how a change of bank details is confirmed and keep it in writing.
The attacks of 2026 and the habit that stops each →
For technology companies

What we read for technology companies.

  • The records that tell inboxes whether to refuse email sent as you (DMARC, SPF and DKIM).
  • Breach records for addresses at your own domain.
  • Names made from yours, each asked whether it is registered and set up for mail.
  • The certificate your website answers with: its name, its dates and who issued it.
  • The headers and cookies your website sends to every visitor.
  • Common addresses for configuration files, code folders and cloud storage.

The rule, from its source: What does each US state's data breach law ask a business to do?

Check my firm

See your own firm the way an attacker reads it.

We read your domain from public records and show each way in with a check anyone can re-run.

Check my firm
05 · Source

Source.

Source: The Hacker News ↗

This page repeats what the source reported, with its date. It says nothing about any firm that is not named in it.