@dgn-src-click-to-pay-org/srcdcfreleasecertnpm
@dgn-src-click-to-pay-org/srcdcfreleasecert is a confirmed malicious npm package (MAL-2026-13744) that opens a backdoor for remote access (malicious versions 374.0.0, 999.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @dgn-src-click-to-pay-org/srcdcfreleasecert (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @dgn-src-click-to-pay-org/srcdcfreleasecert (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @dgn-src-click-to-pay-org/srcdcfreleasecert across your stack and pipelines.
If you installed it — respond
@dgn-src-click-to-pay-org/srcdcfreleasecert establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @dgn-src-click-to-pay-org/srcdcfreleasecert was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @dgn-src-click-to-pay-org/srcdcfreleasecert before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @dgn-src-click-to-pay-org/srcdcfreleasecert-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.