Which versions of emulative are malicious?

The following npm versions of emulative are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate emulative if I installed it?

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

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

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

Search your lockfiles and build artifacts for emulative (version 1.0.1).

Malicious package

emulativenpm

Advisory published Aug 4, 2026Updated Aug 5, 2026

emulative is a confirmed malicious npm package (MAL-2026-11996) 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 emulative (npm)

MAL-2026-11996

Immediate action

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

npm uninstall emulative

What this malware does

On npm install, the package's preinstall lifecycle hook executes index.js, which collects the installer's hostname, username, home directory path, DNS server configuration, and the contents of /etc/passwd and /etc/hosts, then POSTs the aggregated data over HTTPS to the hardcoded host 0645dqp8k07wcnunrmvn0avyepkg87ww.oastify.com (a Burp Collaborator subdomain). The destination is attacker-controlled and unrelated to any documented package function; the collection and exfiltration fire automatically on default install without any user action.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

6e3cf8666b98672329dbb0916b7ef59eac20bce457de82eb40d85b9712e1b4ca

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for emulative (version 1.0.1).
If you installed it — respond
emulative 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 emulative 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. emulative 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-011360

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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