MAL-2026-4737 Malicious code in your-unique-package-name1 (npm)
Malicious package
Published
MAL-2026-4737 is a malicious package: your-unique-package-name1 (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-4737/ (Markdown: https://insights.sbomify.com/MAL-2026-4737/index.md)
- Package
- your-unique-package-name1
- Registry
- npm
What is MAL-2026-4737?
MAL-2026-4737 is a malicious package in your-unique-package-name1, published on 25 May 2026.
Official description
On import in a browser context, index.js creates a hidden iframe pointing at https://www.pendo.io/?builder.frameEditing=true and postMessages a 'builder.patchUpdates' payload to 20 hardcoded builder-<uuid> resources, replacing their '/bindings/show' binding with an injected script. The injected script calls fetch('https://novus-api.pendo.io/pendo/app', {credentials:'include'}), base64-encodes the authenticated response, and beacons it in 2000-byte chunks to https://webhook.site/ea1a1f2d-46e2-463a-a1c1-48c53846dff4 via new Image().src. Any application that bundles this package will silently exfiltrate its end users' authenticated Pendo session data to an anonymous attacker-controlled webhook. The package self-describes as 'Security research PoC' but the destination is not a researcher-owned domain and the targeting (hardcoded victim UUIDs, credentials-included fetch) is consistent with a live attack rather than a contained PoC.
What should I do about MAL-2026-4737?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.