What does the website-scanner malware do?

The obfuscated code in setup.py on installation collects information about the system (all possible about hardware, available resources, IP, names, etc.) and sends to a telegram webhook. Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2024-09-website-scanner Reasons (based on the campaign): - exfiltration-generic - obfuscation - A Telegram webhook is used to send collected data. The OpenSSF Package Analysis project identified 'website-scanner' @ 1.0.0 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of website-scanner are malicious?

The following PyPI versions of website-scanner are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate website-scanner if I installed it?

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

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

Yes — website-scanner is associated with the 2024-09-website-scanner 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 website-scanner 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 website-scanner (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging website-scanner across your stack and pipelines.

Malicious package

website-scannerPyPI

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

Malicious code in website-scanner (PyPI)

MAL-2024-9067

Immediate action

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

pip uninstall website-scanner

What this malware does

The obfuscated code in setup.py on installation collects information about the system (all possible about hardware, available resources, IP, names, etc.) and sends to a telegram webhook.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-09-website-scanner

Reasons (based on the campaign):

exfiltration-generic
obfuscation
A Telegram webhook is used to send collected data.

The OpenSSF Package Analysis project identified 'website-scanner' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

06dde0f250e5ce430d8501b6cecadc7839daed79bdaf46415c8c59f53114fab8

677d8b34d6f083d27ddd6ae3a324aaa6e084f543c1b33c0871abf7b26e571ea9

bab4a414e51f614858ff935138ccb2632b0ba1801566c398a699e692715ccaae

e040b4a75acca156955b5da79b3df464c665bc86727fd87d0e0ee675e96ecc6f

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

Campaign

2024-09-website-scanner

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks website-scanner-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