Which versions of sensadway are malicious?

The following PyPI versions of sensadway are flagged malicious: 0.1, 0.2, 0.3, 0.4, 0.5. Treat any of these as compromised.

How do I remediate sensadway if I installed it?

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

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

Yes — sensadway is associated with the RLMA-2025-03681, GENERIC-standard-pypi-install-pentest, RLUA-2026-00752 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 sensadway 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 sensadway (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sensadway across your stack and pipelines.

Malicious package

sensadwayPyPI

Malicious code in sensadway (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-6582

Immediate action

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

pip uninstall sensadway

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

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: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

5 flagged

0.10.20.30.40.5

Indicators of compromise (SHA-256)

3b30b34031f706e3469774996a74117b284e05d110b82c1ea79ed9edadad387f

ca67628765d388156962681c607b8e280316c7b20af24969cd6346927386b846

bd6ee914063e1d35067f3d6d13bc64aabf1bf7e7e1630f61047b55302f440e67

a621ab5f633595c453c9f65768fef3ccd52c0d8d7c455a8230b9a398e3416697

e4a50cf8cffe030a0a2397803c7e54b98897b575825e1f400ad8ad8b698fe4bb

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

Campaign

RLMA-2025-03681GENERIC-standard-pypi-install-pentestRLUA-2026-00752

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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