Which versions of lnatainstaller are malicious?

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

How do I remediate lnatainstaller if I installed it?

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

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

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

Malicious package

lnatainstallerPyPI

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

MAL-2026-128

Immediate action

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

pip uninstall lnatainstaller

What this malware does

Package is designed to download and execute a remote script, which then downloads and runs a malicious executable

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

Campaign: 2025-12-pdatainstaller

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
malware
Downloads and executes a remote executable.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a613dbd371593bf6bcb7ae528a4d7d7dba2fedfc6670c8cb493bb5cbee18f734

c3822afcab6a1539e1e4fe60243150c1844db475f93311255d63b90c9c8227df

ae050d9062f7f90317c47faea3b14f97ed56d7f427bb69e884f576714abf5e37

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

Campaign

2025-12-pdatainstaller

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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