python-utilsnpm
Malicious code in python-utils (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares "preinstall": "./dist/typecheck.js". The referenced file is not JavaScript — it is a 5,224,556-byte Linux x86 ELF executable (containing __libc_start_main, /lib64, and nux-x86- interpreter strings) with the literal endpoint 207.90.194.2:443 baked into it. The native binary is concealed behind forged TypeScript build metadata: a sibling dist/typecheck.d.ts declares a getParser(): Promise<Parser> API for tree-sitter Python, and dist/typecheck.js.map is a reused copy of parser.js.map (its "file" field is "parser.js"), making the dropper look like ordinary tsdown output to a casual reviewer. On npm install on any Linux x86 host, the ELF runs automatically as the installer's user, calling out to the hardcoded IP:port. The package's stated purpose (a Python utility / tree-sitter parser wrapper) has no legitimate need to ship or execute a native binary at install time, and no pure-JS code path actually consumes getParser.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for python-utils (version 0.2.26). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-utils across your stack and pipelines.
If you installed it — respond
Remove python-utils 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 python-utils 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 python-utils 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks python-utils-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.