GitHub marked four beta releases of the npm package dsh-blue-team-mode as malware and npm removed them.
Anyone who installed one of the four beta releases on 20 November 2026 must treat that computer as compromised. The published code was removed before review, so the payload is not described here.
What happened
GitHub published a reviewed malware advisory for the npm package dsh-blue-team-mode at 20:44 UTC on 20 November 2026.
- The advisory covers versions
3.0.0-beta.17to3.0.0-beta.20and carries no technical detail. - The four releases appeared on npm between 19:21 and 19:39 UTC on 20 November 2026.
- The registry no longer serves those four versions. Requests for
3.0.0-beta.18return 404. - The code was unavailable for inspection, so this page lists advisory and registry facts only.
- Later releases
3.0.0-beta.21to3.0.0-beta.23are not in the advisory. The latest stable release is2.0.0.
Affected versions
3.0.0-beta.17, published 19:24 UTC on 20 November 2026.3.0.0-beta.18, published 19:21 UTC on 20 November 2026.3.0.0-beta.19, published 19:37 UTC on 20 November 2026.3.0.0-beta.20, published 19:39 UTC on 20 November 2026.
How to check
The advisory names no files or hashes, so check your install records for the affected versions.
npm view dsh-blue-team-mode versions
Check your CI build logs and lockfile history for any of the four versions. A clean install today cannot rule out earlier exposure.
What to do now
- If you installed any affected version, remove it and rebuild the environment from a clean package set.
- Treat the computer as fully compromised and rotate all secrets and keys on it from a different machine.
- Stay on the stable
2.0.0release and avoid the3.0.0-betaline until a trusted notice clears it.
What Vigilance would show
These examples show an install hold and the corresponding owner report.
Example install message
Vigilance blocked `dsh-blue-team-mode` 3.0.0-beta.17. This version is too new or changed in a way Vigilance must check first.
Example owner report
Bad update
dsh-blue-team-mode 3.0.0-beta.17
GitHub marked four beta releases of this npm package as malware and npm removed all four the same day.
No security team? See who reads the alert.
Frequently asked questions
What did the malicious code do?
The advisory gives no technical detail and the four versions are gone from npm. Nobody can describe the payload from the published record.
Is the latest beta release safe?
The advisory covers versions 3.0.0-beta.17 to 3.0.0-beta.20 only. Later beta releases and the stable 2.0.0 release are not in it.
Where can I read the advisory?
GitHub hosts the reviewed malware advisory as GHSA-7r7x-px4j-w4jg in its advisory database.
Sources
Send this page to the person who looks after AI at your company.