What does the test-package-avinav malware do?

During installation, a heavily obfuscated code is executed. Exact behaviour unclear Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2025-07-test-package-avinav Reasons (based on the campaign): - obfuscation The OpenSSF Package Analysis project identified 'test-package-avinav' @ 0.0.1 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of test-package-avinav are malicious?

The following PyPI versions of test-package-avinav are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate test-package-avinav if I installed it?

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

If test-package-avinav 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 test-package-avinav part of a known attack campaign?

Yes — test-package-avinav is associated with the 2025-07-test-package-avinav 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 test-package-avinav 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 test-package-avinav (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-package-avinav across your stack and pipelines.

Malicious package

test-package-avinavPyPI

Malicious code in test-package-avinav (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-5837

Immediate action

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

pip uninstall test-package-avinav

What this malware does

During installation, a heavily obfuscated code is executed. Exact behaviour unclear

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

Campaign: 2025-07-test-package-avinav

Reasons (based on the campaign):

obfuscation

The OpenSSF Package Analysis project identified 'test-package-avinav' @ 0.0.1 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a701dbfb1fb2a151d070e86ea07710e08c317743ac5b90d82b3cdc2231cd3093

4c69d3b95e98adbec500b9d5d30b140e8b0ca8134f67c29e625ce1f1cc493468

db665678ac908b6f9aa76ef069759ebd70b62c901a6f840b765ba7cac299c423

dc06b9c4431039005279fe9c2c1dc4e7e88b286bfd61f17bc3be05701f7d0e6a

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

Campaign

2025-07-test-package-avinav

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks test-package-avinav-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