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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for @thepayulink/server (version 2.0.0).

Malicious package

@thepayulink/servernpm

Advisory published Jul 16, 2026Updated Jul 16, 2026

@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
Search your lockfiles and build artifacts for @thepayulink/server (version 2.0.0).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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