GitHub flags taskpace as malware. npm has replaced its removed releases with a security holding package.
GitHub published reviewed malware advisory GHSA-73wm-q362-6xp2 for taskpace on 11 November 2026.
This page reports the advisory and npm registry facts. The removed releases were unavailable for code inspection.
What happened
GitHub classified the package as malware.
- The advisory lists every version as affected and provides no patched version.
- npm records releases
1.0.0on 27 September 2026 and1.1.0on 28 September 2026. - The registry no longer serves those releases. Its latest version is
0.0.1-security, described as a security holding package. - The current registry maintainer is
npm. This metadata confirms the holding status, but does not describe the removed payload.
Affected versions
- The advisory range is
>= 0. - The original releases named in the registry timeline are
1.0.0and1.1.0. 0.0.1-securityis the registry holding package, not a restored original release.
How to check
Check your project dependency tree for the package and version. This command reads installed metadata and does not execute the package.
npm ls taskpace
What to do now
GitHub advises treating machines that installed or ran an affected release as compromised.
- Remove the affected package.
- From a separate computer, rotate secrets and keys stored on the affected machine.
- Do not assume package removal removes every malicious component.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `taskpace` 1.1.0. This version is too new or changed in a way Vigilance must check first. The last safe version is 1.0.0. Install that version.
In the owner report
Bad update
taskpace 1.1.0
This update now downloads from the internet and runs other programs. The version before it did not.
- Ask the AI tool to swap taskpace to 1.0.0. That is the last safe version.
Frequently asked questions
What did the malicious code do?
The advisory gives no payload analysis, and the removed releases were unavailable for inspection. This page does not claim a verified technical mechanism.