{"id":"MAL-2026-14222","revision":"f51e03261b134baab7c28086b8eeaac4","records":[{"revision":"f51e03261b134baab7c28086b8eeaac4","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14222","aliases":[],"title":"Malicious code in streak-cal-core (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (a4e42ea741c3a61878fa72cd8b7ab4547c52f14b69f429129c46edba70771287)\nindex.mjs (the package's main entry) contains a ~500 KB base64-encoded x86-64 ELF payload stored in a `_store` array disguised with a `// --- Calibration Data ---` comment. On import, the module joins the base64 chunks, writes the decoded bytes to disk with mode 0o755, dynamically imports `node:child_process`, and executes the dropped binary. The behavior fires as a top-level import side effect, so any consumer that `require`s or `import`s the package runs the embedded native code. The file's header comment labels the module `streak-larq-hydration` and references `svelte-insight-hydration`, while the package is published as `streak-cal-core` with a README pointing at `svelte-streak-cal` — internal naming does not match the published identity, consistent with a family of sibling typosquat variants. The advertised purpose (dependency-free calendar/streak math helper) is inconsistent with shipping and executing an opaque native binary.\n","state":0,"publishedAt":"2026-08-19T03:02:12+00:00","modifiedAt":"2026-08-19T03:30:19.7551326+00:00","affected":[{"ecosystem":"npm","name":"streak-cal-core","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/streak-cal-core/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14222","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14222","identifiers":["MAL-2026-14222"]},"retained":false,"historicalAffected":[]}],"coverage":[]}