Which versions of typelimagic are malicious?

The following PyPI versions of typelimagic are flagged malicious: 1.0.0, 1.1.0, 1.1.1, 1.1.2, 1.1.3. Treat any of these as compromised.

How do I remediate typelimagic if I installed it?

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

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

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

Malicious package

typelimagicPyPI

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

MAL-2026-2963

Immediate action

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

pip uninstall typelimagic

What this malware does

Clone of a legitimate library. The added code scans system for sensitive files, with the focus on crypto currency wallets, and exfiltrate them. Previous versions included executing remote commands.

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

Campaign: 2026-04-typelimagic

Reasons (based on the campaign):

obfuscation
clones-real-package
crypto-related
exfiltration-crypto
The package contains code to execute remote commands (probably limited to a specific set) on the victim's machine.

Malicious versions

5 flagged

1.0.01.1.01.1.11.1.21.1.3

Indicators of compromise (SHA-256)

7fcef0c386cca43024460aa4a1b47a99109e4ba02159a8fbe426c12f9884a83e

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

Campaign

2026-04-typelimagic

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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