Which versions of tego-managed-agents-test are malicious?

The following PyPI versions of tego-managed-agents-test are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate tego-managed-agents-test if I installed it?

tego-managed-agents-test 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 tego-managed-agents-test — how do I know if it already compromised me?

If tego-managed-agents-test 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 tego-managed-agents-test part of a known attack campaign?

Yes — tego-managed-agents-test is associated with the 2026-09-tego-managed-agents-test, IN-MAL-2026-020557 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 tego-managed-agents-test 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 tego-managed-agents-test (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tego-managed-agents-test across your stack and pipelines.

Malicious package

tego-managed-agents-testPyPI

tego-managed-agents-test is a confirmed malicious PyPI package (MAL-2026-17183) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tego-managed-agents-test (PyPI)

MAL-2026-17183

Immediate action

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

pip uninstall tego-managed-agents-test

What this malware does

The package's custom install command serializes the entire process environment (dict(os.environ)) to JSON and POSTs it to the hardcoded endpoint https://gateway.tego.security during pip install. The exfiltration runs automatically as part of the install lifecycle without user consent, and exceptions are silently swallowed so no error is surfaced to the installer. Because process environments on developer and CI hosts routinely contain credentials (AWS_ACCESS_KEY_ID/AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, database passwords, and other secret-shaped variables), this indiscriminate bulk-environment upload is a credential-harvesting exfiltration path from installer to a remote author-controlled host.

During installation, the code exfiltrates all environment variables to a remote location.

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

Campaign: 2026-09-tego-managed-agents-test

Reasons (based on the campaign):

exfiltration-env-variables
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

b09488c67894dd74d043a240308c694f0e42464e3a4f371b8d5ebc8a6a589d7b

72c8a01de8d706d83a4b80b845099c11602ba778a392337cad2d9a8a40090b5d

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

Campaign

2026-09-tego-managed-agents-testIN-MAL-2026-020557

References

Credits

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

Detect & block this

O3 blocks tego-managed-agents-test-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

Explore

All malware advisories How O3 detects malware Vulnerability database