Which versions of @thepayulink/server are malicious?

The following npm versions of @thepayulink/server are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate @thepayulink/server if I installed it?

Remove @thepayulink/server from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @thepayulink/server — how do I know if it already compromised me?

If @thepayulink/server 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.

Is @thepayulink/server part of a known attack campaign?

Yes — @thepayulink/server is associated with the IN-MAL-2026-010774 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @thepayulink/server across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @thepayulink/server (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @thepayulink/server across your stack and pipelines.

Malicious package

@thepayulink/servernpm

@thepayulink/server is a confirmed malicious npm package (MAL-2026-10719) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @thepayulink/server (npm)

MAL-2026-10719

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @thepayulink/server

What this malware does

The CommonJS bundle loaded by require('@thepayulink/server') (dist/payulink-server.cjs) hardcodes apiBase to https://eliteyatra.vip as the default destination and attaches the caller-supplied keySecret as an Authorization: Bearer header on outbound order/fetch requests. That destination is unrelated to the package's declared publisher: package.json homepage and README point to payulink.io, and the ESM source at src/index.js targets https://payulink.io/api using Basic auth with pl_live_ keys and paise, whereas the shipped CJS dist targets eliteyatra.vip using Bearer auth with pl_sk_ keys and rupees. The dist bundle is therefore not a build of the shipped src — it is a different SDK glued under the same package name that redirects the caller's PayuLink secret and order data to an author-controlled domain the documented API never references. Any consumer using the documented CommonJS default silently exposes their payment gateway secret key and transaction data to eliteyatra.vip.

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

f0f04014bd624dc0712b8bfb78c53832ef18bf6a178d462b1959df9a8b81ec94

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @thepayulink/server (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @thepayulink/server across your stack and pipelines.
If you installed it — respond
Remove @thepayulink/server from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @thepayulink/server 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 @thepayulink/server 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. @thepayulink/server on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010774

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @thepayulink/server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database