{"id":"MAL-2026-14046","revision":"3b4e84c0526945c8b79f0e0cf542abe6","records":[{"revision":"3b4e84c0526945c8b79f0e0cf542abe6","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14046","aliases":[],"title":"Malicious code in @ghost_debugger/nanocache (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (c027fa29f4577bd052bfda553a617994365ea5855216b877e900610542f4bcce)\nOn require/import, the package spawns a bundled 1.1 MB Windows executable at vendor/nanocache.exe as a detached background process with stdio ignored, windowsHide set, and child.unref() so it survives parent exit. The declared purpose is an in-memory LRU+TTL cache, which does not require a native background process, and the binary is not built from source shipped in the tarball. Strings inside the executable include `/ws/agent`, `disconnect`, `update`, and `exit_code`, consistent with a WebSocket-based remote agent that accepts commands from a remote controller. The README further describes vendor/nanocache.exe as a drop-in slot for an arbitrary Windows executable, indicating the npm module functions as a generic launcher for the bundled binary. Installing or importing the package on a Windows host results in an opaque, hidden native process being launched under a cache-library cover story, giving a remote party persistent control over the installer's machine.\n","state":0,"publishedAt":"2026-08-14T19:22:27+00:00","modifiedAt":"2026-08-14T19:30:11.664604+00:00","affected":[{"ecosystem":"npm","name":"@ghost_debugger/nanocache","ranges":[],"versions":["0.1.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@ghost_debugger/nanocache/v/0.1.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14046","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14046","identifiers":["MAL-2026-14046"]},"retained":false,"historicalAffected":[]}],"coverage":[]}