Which versions of myfirstpackagetestaaa are malicious?

The following PyPI versions of myfirstpackagetestaaa are flagged malicious: 2.26. Treat any of these as compromised.

How do I remediate myfirstpackagetestaaa if I installed it?

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

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

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

Malicious package

myfirstpackagetestaaaPyPI

Malicious code in myfirstpackagetestaaa (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-5875

Immediate action

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

pip uninstall myfirstpackagetestaaa

What this malware does

During installation, the code attempts to download and start a malicious executable.

Likely related to 2025-08-raknet-testing-package.

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

Campaign: 2026-06-easyaillm

Reasons (based on the campaign):

Downloads and executes a remote executable.
obfuscation
malware
tool:mshta

Malicious versions

1 flagged

2.26

Indicators of compromise (SHA-256)

018e4d3e7b58b3cda9063b81957d9b960307e240704e17c99d68227907ec776b

c05b4934471efac919453e87b37a94a9a92c930455283c0bfb85b535c61f4a6b

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

Campaign

2026-06-easyaillm

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks myfirstpackagetestaaa-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