Which versions of sentinel-tool are malicious?

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

How do I remediate sentinel-tool if I installed it?

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

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

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

Malicious package

sentinel-toolPyPI

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

MAL-2026-2516

Immediate action

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

pip uninstall sentinel-tool

What this malware does

The package installs a remote executable that uses a hardcoded Telegram channel for monitoring the user's activity, including regularly taking screenshots, and some remote control possibilities like switching the computer off and grabbing clipboard content. Some content suggests it was designed to be used by the uploader themself, but it poses the risk to anyone installing it.

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

Campaign: 2026-04-sentinel-tool

Reasons (based on the campaign):

Downloads and executes a remote executable.
spyware-like

Malicious versions

6 flagged

0.10.20.30.40.50.6

Indicators of compromise (SHA-256)

5a2ff07802c4546c40d47d3780971506115297a1e8c177be36ad1e003dd62937

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

Campaign

2026-04-sentinel-tool

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks sentinel-tool-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