MAL-2026-13744 Malicious code in @dgn-src-click-to-pay-org/srcdcfreleasecert (npm)
Malicious package
Published
MAL-2026-13744 is a malicious package: @dgn-src-click-to-pay-org/srcdcfreleasecert (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-13744/ (Markdown: https://insights.sbomify.com/MAL-2026-13744/index.md)
- Package
- @dgn-src-click-to-pay-org/srcdcfreleasecert
- Registry
- npm
What is MAL-2026-13744?
MAL-2026-13744 is a malicious package in @dgn-src-click-to-pay-org/srcdcfreleasecert, published on 11 Aug 2026.
Official description
The package's postinstall script POSTs installer metadata (package name/version, platform, arch, Node version, timestamp) over plain HTTP to a hardcoded sslip.io-wrapped bare IP at http://16-171-38-148.sslip.io:8080/api/install. The scoped name mimics an internal corporate org (@dgn-src-click-to-pay-org) and the version is inflated to 374.0.0, matching the canonical dependency-confusion pattern: a lure package published to the public registry to be resolved by internal build systems that mistakenly reach out for a namespace they expected to be private, with a callback that reports successful installs to an attacker-controlled endpoint. The beacon fires automatically on npm install with no user action, revealing internal build host presence and confirming which corporate targets are vulnerable to further dependency-confusion payloads.
What should I do about MAL-2026-13744?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.