# MAL-2026-10441: Malicious code in turbocalcng (PyPI)


- **Type:** Malicious package
- **Package:** `turbocalcng` (PyPI)
- **Published:** 13 Jul 2026

## What is MAL-2026-10441?

MAL-2026-10441 is a malicious package in turbocalcng, published on 13 Jul 2026. 

### Official description

turbocalcng/__init__.py imports arithmetic.py, which — beneath a facade of arithmetic helpers — contains an XOR-obfuscated in-memory native code execution path reachable at import time. A helper iReferringj(k,d) XOR-decodes byte lists into the strings 'base64', 'ctypes', 'mmap', 'threading', 'CFUNCTYPE', 'Thread', 'daemon', 'start', etc., and resolves them dynamically via getattr / __import__ / importlib.util.spec_from_file_location to hide the dangerous imports from static review. The reachable loader allocates an RWX region with mmap.mmap(-1, size, prot=7, flags=34), writes decoded bytes into it, casts the region's address through ctypes.CFUNCTYPE and invokes it inside a daemon threading.Thread — executing attacker-supplied native code in the installer's Python process on `import turbocalcng`. The obfuscation of core module names alongside the RWX + function-pointer-cast + thread-start primitive is characteristic of hostile shellcode injection, not any legitimate arithmetic functionality.

During import an obfuscated code starts in-memory functions from a binary blob; after that, it communicates with dockfinancial[.]lu, the exact behaviour is unknown.

---

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

Campaign: 2026-07-turbocalc

Reasons (based on the campaign):

 - obfuscation

 - other

## What should I do about MAL-2026-10441?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10441 is a malicious package: turbocalcng (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10441/ (Markdown: https://insights.sbomify.com/MAL-2026-10441/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10441

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10441/
Summaries are generated and may contain mistakes; the official description above is the record.