Which versions of taskforge-9xv are malicious?

The following npm versions of taskforge-9xv are flagged malicious: 1.3.0. Treat any of these as compromised.

How do I remediate taskforge-9xv if I installed it?

Remove taskforge-9xv 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.

I already installed taskforge-9xv — how do I know if it already compromised me?

If taskforge-9xv 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.

Is taskforge-9xv part of a known attack campaign?

Yes — taskforge-9xv is associated with the IN-MAL-2026-019483 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find taskforge-9xv across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for taskforge-9xv (version 1.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging taskforge-9xv across your stack and pipelines.

Malicious package

taskforge-9xvnpm

taskforge-9xv is a confirmed malicious npm package (MAL-2026-15914) that executes malicious code on install (malicious version 1.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in taskforge-9xv (npm)

MAL-2026-15914

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall taskforge-9xv

What this malware does

The taskforge CLI, once configured with an origin URL via taskforge setup --origin-server <url>, fetches bytes from <origin>/api/x-handler and pipes them into a detached node - process (spawn(process.execPath, ['-'], {detached:true,...}) with the response body written to stdin). There is no hash, signature, or shape verification — only a >100-byte length gate. The spawned worker records its PID and is respawned on version change, giving whoever controls the configured origin a persistent remote code-execution channel on the host: the served payload can be rotated at will. The package reinforces this shape with cover-story naming (taskforge-9xv with a random suffix, description 'Runtime delivery client (private data layout)'), single-letter/renamed identifiers (edap, dRB, esd, gapid, dl, spn, sPid), a randomized 8-byte-hex data directory under ~/.local/share/taskforge/, and a README stating the directory and filenames are intentionally not descriptive. The origin is caller-supplied rather than hardcoded, but the delivered code runs unchecked in the background regardless of who operates that origin.

Malicious versions

1 flagged

1.3.0

Indicators of compromise (SHA-256)

1b03d2c3ed0eec654a85d7843b208bdca926027df8dac14aa881f50c21a08f40

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for taskforge-9xv (version 1.3.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging taskforge-9xv across your stack and pipelines.
If you installed it — respond
Remove taskforge-9xv 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-9xv 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-9xv 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

No. taskforge-9xv on npm has been identified as a malicious package (version 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019483

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks taskforge-9xv-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database