Forensia CTI Core

Summary

Ingested excerpt (first ~500 chars of normalized text).

How to Use Transformers.js in a Chrome Extension How to Use Transformers.js in a Chrome Extension Hugging Face Models Datasets Spaces Buckets new Docs Enterprise Pricing Log In Sign Up Back to Articles How to Use Transformers.js in a Chrome Extension Published April 23, 2026 Update on GitHub Upvote 32 +26 Nico Martin nico-martin Follow Who this is for What we will build 1) Chrome extension architecture (MV3) 1.1 Runtime contexts and entry points 1.2 What runs where 1.3 Messa…

https://huggingface.co/blog/transformersjs-chrome-extension

sha256:d3b1e796d63dafd0284752852f312344f9e113a5edfc494d0391ac079ce98590

What we pulled out

Deterministic extractor (IOC + allowlisted tokens + ATT&CK IDs present in DB).

cve0
md51
url0
ipv40
ipv60
sha10
domain16
sha2560
malware_token0
attack_pattern0
threat_actor_token0

Indicators

Linked with report → mentions → indicator. Values open the indicator workspace.

Type	Value	Link
domain	github.com	Open →
domain	index.html	Open →
domain	agent.runagent	Open →
domain	manifest.json	Open →
domain	background.ts	Open →
domain	sidebar.html	Open →
domain

Malware families

Allowlist token matches only.

None extracted.

Threat actors mentioned

Allowlist mentions — not a formal attribution verdict.

None extracted.

ATT&CK techniques

MITRE IDs referenced in text and present in local technique table.

None linked (import ATT&CK or adjust text).

CONTINUE INVESTIGATION

High-signal pivots without leaving the thread you started in search.

All reports
Browse the report corpus.
Intel graph (first IOC)
Neighborhood from the first linked indicator.

← Back to reports