Which versions of res-adapter are malicious?

The following PyPI versions of res-adapter are flagged malicious: 912.6. Treat any of these as compromised.

How do I remediate res-adapter if I installed it?

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

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

Yes — res-adapter is associated with the RLMA-2024-11149, 2024-11-byted-dast, RLUA-2026-00719 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 res-adapter 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 res-adapter (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging res-adapter across your stack and pipelines.

Malicious package

res-adapterPyPI

Malicious code in res-adapter (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-11692

Immediate action

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

pip uninstall res-adapter

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

Malicious versions

1 flagged

912.6

Indicators of compromise (SHA-256)

0c17bb8a001360f9ff779cf682de08ec365756a86106915b898f63c6ed80742e

d7ab6c30b61be1896e6dbb9ffa2a131df7b5b2dcafc9d82449d17f8674b9b045

3a155b2a75481fd706ee3be40276e4c58c0a3ff15a01d86ff2e79f623c2e7c0c

a0f6d9725975fa09f66d80f3ae699481d721594d1cf53aeb0347140c52cf342d

210e70ab874423621f2ec89184801a1c3457b2e337293cdaf033c6f71b088834

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 res-adapter (version 912.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging res-adapter across your stack and pipelines.
If you installed it — respond
res-adapter 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 res-adapter 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 res-adapter 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. res-adapter on PyPI has been identified as a malicious package (version 912.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-111492024-11-byted-dastRLUA-2026-00719

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks res-adapter-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