# PyPI nousergon-lib Malicious Package Reference in Process Execution

- **Severity:** Critical
- **Signature ID:** `3e8a1c2b-6f47-4b9a-9e21-7d5f8c4a1b6e`
- **MITRE ATLAS:** AML.T0010 (AI Supply Chain Compromise)
- **OWASP:** LLM05 (Improper Output Handling)

## Summary

A package called nousergon-lib, posing as a shared AWS/logging/AI-integration helper for 'Nous Ergon' modules, is suspected of being trojanized. This detection flags any attempt to actually install, import, or execute it on a system.

## How the attack works

An attacker publishes a lookalike package to PyPI under a plausible-sounding name tied to internal-style tooling (AWS, logging, AI integration). A victim, likely through a typo, a poisoned dependency list, or social engineering, installs it via pip, pip3, poetry, pipenv, or uv, or imports it directly in Python, or runs its setup.py. Once installed, the package can execute arbitrary code with the privileges of the user or service running it. This rule watches command-line activity for any command that actually installs or runs the package rather than just mentioning its name.

## Why it matters

If installed, a trojanized package runs attacker code inside the victim's environment, which can lead to credential theft, further supply-chain compromise, or unauthorized access to cloud resources like AWS.

## What you can do

- Search your dependency manifests, lockfiles, and container images for any reference to nousergon-lib version 0.124.131.
- If found installed, treat the host or environment as compromised: isolate it, rotate any credentials or AWS keys it had access to, and investigate for further activity.
- Pin and review dependencies before adding new AI-integration or utility packages, especially ones not from a known, verified publisher.
- Run SBOM or dependency-audit tools regularly to catch known-malicious package names before they are installed, not just after.

## Known benign look-alikes

- Security or SBOM scanning tools (pip-audit, safety, syft, grype, trivy, osv-scanner) auditing dependency manifests or lockfiles for known-malicious package names without installing them
- Read-only inspection commands (grep, cat, less, more, head, tail, find, echo, pip show/list/freeze) run during incident response to check whether the package appears in requirements files or installed package lists
- Automated dependency-review or CI reporting pipelines that print, log, or diff the package name for an advisory report without installing or importing the library

## References

- https://pypi.org/project/nousergon-lib/

---
Source: https://www.netzilo.com/threats/pypi-nousergon-lib-malicious-package