Malicious code in sigchain-js (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-11146
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (034ba6bdd11139e40b062606dfa180a60727249035899eded96d34797b63a026) The published dist bundles (dist/sigchain-js.cjs.js, dist/sigchain-js.esm.js, dist/sigchain-js.umd.js) contain top-level code that reads an encrypted payload from a companion package (esm imports `desKey` from the `thedata` package; cjs/umd reads `node_modules/tchain-api/apps/docs/app/rsa.db`), DES-decrypts it using the hardcoded password "hydra", spawns a detached `node` child process, and pipes the decrypted string into that subprocess's stdin for execution. This code is not present in the src/ tree — it appears only in the published dist bundles, along with new top-level imports of `child_process`, `node:fs`, `node:path`, and (esm) `desKey` from `thedata` that do not exist in source. The dropper is split across cooperating packages: `thedata` (declared as a direct dependency) supplies the encrypted payload for the esm build, and `tchain-api` (a look-alike of Theta's official API SDK, pulled in transitively) supplies `apps/docs/app/rsa.db` for the cjs/umd builds. The package also pins `[email protected]`, a version that does not exist in the legitimate axios release history, redirecting the installer to a squatted namesake. Requiring or importing sigchain-js results in arbitrary code execution on the installer's host, with the executed content controlled by whoever publishes updates to the companion packages. ## Source: ghsa-malware (104d25d6fa2b72141154551a4a50ea8c6a496d4fc1ce6fd212207d4fe321ee4b) 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.
- Source published
- 28 Jul 2026 13:36:13 UTC
- Source modified
- 20 Aug 2026 18:30:12 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.