Which versions of raylink are malicious?

The following PyPI versions of raylink are flagged malicious: 92.6. Treat any of these as compromised.

How do I remediate raylink if I installed it?

raylink 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 raylink — how do I know if it already compromised me?

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

Yes — raylink is associated with the 2024-11-byted-dast 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 raylink across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for raylink (version 92.6).

Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →

Malicious package

raylinkPyPI

Advisory published Nov 6, 2024Updated Dec 12, 2025

raylink is a confirmed malicious PyPI package (MAL-2024-10587) that steals credentials and exfiltrates sensitive data (malicious version 92.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in raylink (PyPI)

MAL-2024-10587

Immediate action

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

pip uninstall raylink

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: 2024-11-byted-dast

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'raylink' @ 92.6 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

92.6

Indicators of compromise (SHA-256)

23afd02ac19f5910b3875c451e2d44d6edf310a27bb0bdf6716f42fb3438c5c6

977a59faaf2c6fc0d5eacf754dd6a41225eda2882c52d7a83483e830797973d7

0613226708c4c024ae1a37260c710abacbdc1b58cf53952873e39d134bb4c3a7

2a31fad9950db5f7784eca562400fac9fd80a6922ea76f050d7b05bdce7c0928

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for raylink (version 92.6).
If you installed it — respond
raylink 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 raylink 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. raylink on PyPI has been identified as a malicious package (version 92.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks raylink-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

Explore

All malware advisories How O3 detects malware Vulnerability database