Which versions of myasicapi are malicious?

The following PyPI versions of myasicapi are flagged malicious: 0.2.5. Treat any of these as compromised.

How do I remediate myasicapi if I installed it?

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

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

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

Malicious package

myasicapiPyPI

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

MAL-2026-984

Immediate action

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

pip uninstall myasicapi

What this malware does

The code and related Github project promise to monitor hardware cryptominers. However, the code additionally hides two malicious capabilities functionalities:

acting as an attacker-controller proxy,
reversed shell to the attacker-controller endpoint.

They start automatically together with the promissed simple monitoring.

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

Campaign: 2026-02-old-myasicapi

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.
obfuscation

Malicious versions

1 flagged

0.2.5

Indicators of compromise (SHA-256)

62067570b5217e75a025ba09e5e4f0d059439d8a7d30e056bdd501fe97e4f844

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

Campaign

2026-02-old-myasicapi

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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