NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

certify-webPyPI

Advisory published Updated

certify-web is a confirmed malicious PyPI package (MAL-2026-20257) that steals credentials and exfiltrates sensitive data (malicious version 0.1.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in certify-web (PyPI)

MAL-2026-20257
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall certify-web

What this malware does

On pip install certify-web, setup.py's install command invokes ensure_ninja_agent(), which downloads a NinjaOne remote-management.deb from eu.ninjarmm.com hardcoded to the author's tenant (organization UUID e9f1a699-f8b3-4386-9d2d-68cb8f3e3801, 'Oficinaprincipal') and installs it via dpkg -i on Linux amd64/arm64. A shipped.pth file (import certify_web_postinstall; certify_web_postinstall.run()) re-runs the same ensure-agent path on every Python interpreter start. The installed NinjaOne agent is launched as a daemon (DAEMON_RUN=1) and provides the tenant operator with remote shell, arbitrary script execution, file transfer, and software deployment on the enrolled host; enrollment is not caller-configurable. container_runtime.install_runtime_scripts writes /usr/local/bin/certify-web-ninja-keepalive.sh, /usr/local/bin/certify-web-ninja-on-boot.sh, and /etc/xdg/autostart/certify-web-ninja.desktop, and spawns a nohup keepalive loop that re-runs the ensure-agent path every 60 seconds, resurrecting the agent after reboots or process kills. Evasion steps include a fake systemctl shim prepended to PATH during dpkg to bypass the vendor preinst's refusal to install without systemd (e.g., inside containers), and a spoofed Chrome User-Agent on the.deb download. The package name and description do not disclose any of this behavior.

Package installs a PTH file that during every Python startup installs a NinjaOne (legitimate remote management tool) agent tied to the attacker-controlled account and ensures its persistence. As such, the attacker gains full control over the machine.

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

Campaign: 2026-11-certify-web

Reasons (based on the campaign):

  • rat

  • abuses-pth

  • persistence

Malicious versions

1 flagged
0.1.3

Indicators of compromise (SHA-256)

0967f829a27c14c8f6fdec12a380352683e1752bb117a4c8bec3c9554844b797
3632ae3bbd980743b5a64d69c328ad10e35ed1998c202f3e4a437d687f31f7a3

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for certify-web (version 0.1.3).

  2. If you installed it — respond

    certify-web 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.

  3. Did it already run?

    If certify-web was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. certify-web on PyPI has been identified as a malicious package (version 0.1.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-11-certify-webIN-MAL-2026-022909

References

Credits

  • Amazon Inspector · finder
  • Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks certify-web-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

certify-web (PyPI) malicious package — MAL-2026-20257 | O3 Security