Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@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 version 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)

MAL-2026-13744
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @dgn-src-click-to-pay-org/srcdcfreleasecert

What this malware does

The package's postinstall hook (scripts/check-env.js) executes on npm install and POSTs the package name/version along with the host's platform, architecture, and Node.js version to a hardcoded bare-IP endpoint at http://16-171-38-148.sslip.io:8080/api/install over plain HTTP. The package is published at version 999.0.1 — a sentinel value chosen to outrank legitimate internal versions during resolution — under a scoped organization name evoking a payments vendor (Discover/SRC click-to-pay), while the module body contains only trivial PAN/Luhn helpers. This is the canonical dependency-confusion reconnaissance shape: the squatted scope resolves inside a target build system and the postinstall beacon reports back which internal environments were successfully hijacked, enabling attacker follow-up against those hosts.

Malicious versions

1 flagged
999.0.1

Indicators of compromise (SHA-256)

6c203676b4cd54080189fef8d6740d09a1667f2ba0d939936ee46bd6dda4e15d

Detection & response playbook

Backdoor / remote access

  1. Find 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 (version 999.0.1). 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.

  2. 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.

  3. 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.

  4. 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

No. @dgn-src-click-to-pay-org/srcdcfreleasecert on npm has been identified as a malicious package (version 999.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017386

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@dgn-src-click-to-pay-org/srcdcfreleasecert (npm) malicious package — MAL-2026-13744 | O3 Security