Malicious code in assertcoreutils (npm)
-= Per source details. Do not edit below this line.=-
assertcoreutils impersonates the popular chai assertion library: the README, the chai keyword, the lib/chai/ directory layout, and lib/chai.js are copied verbatim from chai. When a consumer runs require('assertcoreutils'), index.js calls child_process.spawn('node', ['lib/chai/utils/addAssertion.js',...], { detached: true, stdio: 'ignore' }) followed by .unref(), launching a hidden, detached child that survives the parent and produces no console output. lib/chai/utils/addAssertion.js is encoded with obfuscator.io string-array / RC4-base64 obfuscation (hex-named identifiers _0x2ff01b, _0x516b, etc.) that hides a hardcoded HTTPS URL plus query-key; the child performs an HTTPS GET to that URL and passes the response body into new Function('require', body)(require), giving the remote operator arbitrary Node-level code execution on every installer. The combination of typosquat lure, copied legitimate package contents as cover, obfuscated remote URL, detached silent child, and runtime new Function over fetched bytes is a supply-chain dropper.
왜 이 VPI인가 (설명가능 · 실험적)
VPI 산정 기준
| 영향도(기본값(정보 없음)) | 55.00 |
| 악용 신호(추가 악용신호 없음) | ×1.00 |
| VPI | 55.00 |
VPI 공식 vpi-v1 기준