taskforge-8xvnpm
taskforge-8xv is a confirmed malicious npm package (MAL-2026-15913) that executes malicious code on install (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in taskforge-8xv (npm)
What this malware does
The package's sole function is a runtime loader that fetches a JavaScript payload from a configured origin's /api/x-handler endpoint and executes it in memory by piping the bytes into a detached node - child process (spawn(process.execPath, ["-"], {detached:true, stdio:["pipe","ignore","ignore"], windowsHide:true})). No signature or hash verification is performed and the README explicitly states client contents are not verified. Supporting evasion characteristics are present: state is kept in a random 8-byte hex subdirectory under the app-data root with a pointer.json indirection, the child is spawned detached with windowsHide:true and stdio ignored, a prior worker PID is SIGTERM'd before each execution, and the package documents that directory and internal filenames are intentionally non-descriptive. The package supplies no legitimate library functionality beyond executing remote code; whoever controls the configured origin obtains full code execution on the host during any version-check poll.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for taskforge-8xv (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging taskforge-8xv across your stack and pipelines.
If you installed it — respond
Remove taskforge-8xv from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If taskforge-8xv was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks taskforge-8xv before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks taskforge-8xv-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.