MAL-2026-20269: Malicious code in piepa-yfcbf-util (npm)
--- -= Per source details. Do not edit below this line.=-
Source: ghsa-malware (ac1a54c1182da443e76690ce44ea99d4cfa6260c58e539b6eccf004ac273c8d3) 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Remove
Remove
npm/piepa-yfcbf-utilfrom your environment.Remove the piepa-yfcbf-util package; removal may not remove all malicious software resulting from its installation.
- Operational
Immediately rotate all secrets and keys stored on the affected computer, using a different computer.
Event History
Frequently Asked Questions
Who should treat this as an active compromise?
Any computer where the package is installed or running should be considered fully compromised. This includes systems that may have installed it as part of an npm dependency workflow.
What should be done immediately?
Rotate all secrets and keys stored on the affected computer, using a different computer to perform the rotation. Do not rely on the potentially compromised host for credential recovery or replacement.
Is removing the package sufficient to remediate the issue?
No. The package should be removed, but removal does not guarantee that all malicious software installed as a result has been removed, because an outside entity may have obtained full control of the computer.