Which versions of shortneer are malicious?

The following PyPI versions of shortneer are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate shortneer if I installed it?

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

If shortneer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is shortneer part of a known attack campaign?

Yes — shortneer is associated with the 2026-09-sherpy, IN-MAL-2026-020936 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 shortneer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for shortneer (version 0.1.0).

Malicious package

shortneerPyPI

Advisory published Oct 1, 2026Updated Oct 4, 2026

shortneer is a confirmed malicious PyPI package (MAL-2026-17422) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in shortneer (PyPI)

MAL-2026-17422

Immediate action

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

pip uninstall shortneer

What this malware does

The package ships a macOS arm64 Rust-compiled Python extension (_core.abi3.so) fronted by a thin wrapper lb.py. The only exposed Python function, shortname(), invokes two gibberish-named native entrypoints (_core.dphjx0rdhx0 and _core.ioluli0x0xthf) and swallows all exceptions with a silent print(''). The native binary embeds the hardcoded path 'Library/Application Support/Telegram Desktop/tdata' (the installer's Telegram Desktop session store on macOS), the archive name 'fghj.zip', and the destination 'https://api.telegram.org', alongside zip, AES, ChaCha20 and reqwest/rustls/hyper HTTP client code. This matches packaging the installer's live Telegram Desktop session directory and uploading it to a Telegram bot controlled by the author, which grants full takeover of the installer's Telegram account. The random-looking native export names and the blanket exception suppression serve to hide the behavior from casual inspection; the package's self-description as an OSINT utility does not match its actual data flow, which targets the installer's own messaging session store rather than any user-supplied target.

When used, the package exfiltrates Chrome extension files (likely targeting cryptocurrency wallets) and sensitive Telegram files.

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

Campaign: 2026-09-sherpy

Reasons (based on the campaign):

infostealer
exfiltration-crypto
target:telegram
native-extension

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

5e166ae1253c886885381cb5087f67a59a869cad6ece6f3ac40aefc6e463c27f

4960c121d2fbf6337d33df0c6a304f4f3e968d18c64614c323ac5f8389020bab

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for shortneer (version 0.1.0).
If you installed it — respond
shortneer 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 shortneer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. shortneer on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-sherpyIN-MAL-2026-020936

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database