Which versions of internment are malicious?

The following crates.io versions of internment are flagged malicious: 0.8.7. Treat any of these as compromised.

How do I remediate internment if I installed it?

internment establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If internment 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.

How do I find internment across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for internment (version 0.8.7).

Malicious package

internmentcrates.io

Advisory published Aug 20, 2026Updated Aug 20, 2026

internment is a confirmed malicious crates.io package (MAL-2026-14337) that opens a backdoor for remote access (malicious version 0.8.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internment (crates.io)

MAL-2026-14337

Immediate action

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

remove internment

What this malware does

internment 0.8.7 was published to crates.io from the same maintainer account (droundy) as the trojanized arrayref and append-only-vec releases, which appears to be compromised. The release adds a dependency on an attacker-controlled crate whose build script downloads and executes an architecture-specific remote binary at build time from https://23.254.165.112:9089/, passing 23.254.165.112:443 as a command-and-control address. Part of a coordinated crates.io campaign on 2026-08-20. The malicious release has been removed from crates.io; earlier internment releases are unaffected.

Malicious versions

1 flagged

0.8.7

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for internment (version 0.8.7).
If you installed it — respond
internment establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If internment 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. internment on crates.io has been identified as a malicious package (version 0.8.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

SafeDep · finder
jhobern · reporter

Detect & block this

O3 blocks internment-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database