AI-driven development workflow commands for any project. Scaffolds a complete PRD-to-PR pipeline with multi-platform AI assistant support.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-19178 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-19178 confirms this npm version as malicious.
Advisory
MAL-2026-19178
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brunosps00/dev-workflow (npm)
Details
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The package is not malicious by the install-hook policy because it has no lifecycle scripts and the risky behavior follows explicit CLI commands. It warrants a warning because those commands modify broad project agent control surfaces and register automatically executed hooks.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs dev-workflow init, update, or repair in a project.
Impact
Later Claude-compatible sessions can load package-supplied skills, MCP commands, and hooks; install-deps can fetch and execute named third-party tools when separately invoked.
Mechanism
Project agent configuration, MCP registration, and hook installation.
Avoid installing @brunosps00/dev-workflow@2.3.0. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.