Which versions of rs-lookout-sandbox-poc are malicious?

The following npm versions of rs-lookout-sandbox-poc are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate rs-lookout-sandbox-poc if I installed it?

rs-lookout-sandbox-poc 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 rs-lookout-sandbox-poc — how do I know if it already compromised me?

If rs-lookout-sandbox-poc 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 rs-lookout-sandbox-poc part of a known attack campaign?

Yes — rs-lookout-sandbox-poc is associated with the IN-MAL-2026-021548 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 rs-lookout-sandbox-poc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rs-lookout-sandbox-poc (version 1.0.1).

Malicious package

rs-lookout-sandbox-pocnpm

Advisory published Oct 20, 2026Updated Oct 20, 2026

rs-lookout-sandbox-poc is a confirmed malicious npm package (MAL-2026-18109) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rs-lookout-sandbox-poc (npm)

MAL-2026-18109

Immediate action

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

npm uninstall rs-lookout-sandbox-poc

What this malware does

On module load, index.js reads os.userInfo().username and issues an HTTPS GET to a hardcoded third-party collector at https://webhook.site/553dad0e-c841-46a8-b07d-213b52a24686/, transmitting the installer's local username to an anonymous external endpoint. The same top-level code performs AWS Instance Metadata Service reconnaissance against 169.254.169.254: it PUTs /latest/api/token to obtain an IMDSv2 session token and then GETs /latest/meta-data/iam/security-credentials/ to enumerate the IAM role attached to the host. Both behaviors fire automatically when the package is required, with no caller action.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

4f28ed1c404dad5afc7b70b345eeef6f81e04dcee77be3a7553956c7a43f8e7c

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rs-lookout-sandbox-poc (version 1.0.1).
If you installed it — respond
rs-lookout-sandbox-poc 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 rs-lookout-sandbox-poc 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. rs-lookout-sandbox-poc on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021548

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rs-lookout-sandbox-poc-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