Which versions of rendezvous-js are malicious?

The following npm versions of rendezvous-js are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate rendezvous-js if I installed it?

rendezvous-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed rendezvous-js — how do I know if it already compromised me?

If rendezvous-js 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 rendezvous-js part of a known attack campaign?

Yes — rendezvous-js is associated with the IN-MAL-2026-003542, IN-MAL-2026-003543 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 rendezvous-js 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 rendezvous-js (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rendezvous-js across your stack and pipelines.

Malicious package

rendezvous-jsnpm

Malicious code in rendezvous-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4662

Immediate action

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

npm uninstall rendezvous-js

What this malware does

On npm install (scripts.install runs node index.js) and on require('rendezvous-js'), lib/core.js collects os.userInfo().username, os.hostname(), and the basename of process.cwd(), then issues a DNS A-record lookup for lwrendezvous.<user>.<host>.<cwd>.<timestamp>.oob.sl4x0.xyz. The query encodes installer host identity into the subdomain so it reaches the attacker's authoritative nameserver — a standard DNS-tunnel exfiltration channel that bypasses HTTP egress filtering. The destination domain (oob.sl4x0.xyz), the imported module names (os, dns, process), and method names (userInfo, hostname, cwd, resolve4) are all stored as decimal char-code arrays in lib/b02e30.js and lib/6ad264.js and decoded at runtime via String.fromCharCode solely to hide the channel from review. The README explicitly claims 'No network requests / No file system access', directly contradicting the shipped code. The author email [email protected] matches the exfil domain, and the beacon prefix lwrendezvous plus generic 'Enterprise Tools Team' authorship are consistent with a typosquat/dependency-confusion lure. Installer harm fires both at install time and at require time without consent.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

5b4a03eaa6b09e5b9e291dd450f58e49a639c3efd8fa952f5ac48f9aea04aba4

94439c9366c8f8c3ae7ed2b70305f1ea90efca3e5d162868f3453b7237f7a5c5

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rendezvous-js (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rendezvous-js across your stack and pipelines.
If you installed it — respond
rendezvous-js is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rendezvous-js 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 rendezvous-js 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. rendezvous-js on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003542IN-MAL-2026-003543

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rendezvous-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring