Which versions of watchitoring are malicious?

The following PyPI versions of watchitoring are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate watchitoring if I installed it?

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

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

Yes — watchitoring is associated with the RLMA-2025-02014, 2025-02-multis, RLUA-2026-00913 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 watchitoring 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 watchitoring (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging watchitoring across your stack and pipelines.

Malicious package

watchitoringPyPI

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

MAL-2025-3015

Immediate action

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

pip uninstall watchitoring

What this malware does

Infostealer with multiple possibilities, but not auto-activating on installation. There are already multiple attempts to publish it, with different innocent-looking names.

The campaign contains the with Infostealer itself and packages that include it as dependency and triggered.

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

Campaign: 2025-02-multis

Reasons (based on the campaign):

infostealer
The malicious code is intentionally included in a dependency of the package

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

ac40257ceeca8a5d1426d3ddf5c364d3e31a953964d3aa4c1d2384b8de440f74

ff391e12bfdd85488464b90c8666148af6d177b2620ce2637e19ea67391e1794

0b2a1b7442e643963d1f4aa3fe8696741f7ed248d39effb173f8d77e37690066

70c42535b6ba7391e60825a2ed0bf740a7c0027db0a5c519a044872655cda3d4

a1448f4896564382ce7b0ed7dc383317f29ce97dafcfa6af130ada330927f568

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

Campaign

RLMA-2025-020142025-02-multisRLUA-2026-00913

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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