Which versions of in-install are malicious?

The following npm versions of in-install are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate in-install if I installed it?

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

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

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

Malicious package

in-installnpm

in-install is a confirmed malicious npm package (MAL-2026-13982) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in in-install (npm)

MAL-2026-13982

Immediate action

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

npm uninstall in-install

What this malware does

[email protected] declares its ltidisafe dependency as an HTTPS tarball URL hosted on a Google Cloud Storage bucket (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-3.6.9.tgz) rather than a registry-resolved package. Running npm install in-install fetches that tarball and installs it into the installer's node_modules, executing whatever install/import-time code it ships. The bucket path is mutable by whoever controls it, is not subject to npm registry review, and is not pinned to a registry-audited artifact, so the bytes delivered at install time can be changed at any moment without a version bump. The package's own index.js is an empty export; the sole observable effect of installing it is pulling arbitrary off-registry code into the installer's environment.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

58b0bedeac5b8460ad12e0ef3e013f8146eb2b7adacd483c3b8833f1dcbb457b

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

Campaign

IN-MAL-2026-017684

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks in-install-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

Explore

All malware advisories How O3 detects malware Vulnerability database