Which versions of openmct-couch-plugin are malicious?

The following npm versions of openmct-couch-plugin are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate openmct-couch-plugin if I installed it?

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

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

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

Malicious package

openmct-couch-pluginnpm

Malicious code in openmct-couch-plugin (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4629

Immediate action

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

npm uninstall openmct-couch-plugin

What this malware does

On npm install, the package's preinstall script runs node index.js and then curls the output of hostname && whoami to http://8irluql1d21jmq8tr5n5fyoxjopfdd12.oastify.com/nasa/couchrestore/ over plain HTTP. The bundled index.js additionally reads /etc/passwd, captures whoami/id, os.hostname(), os.platform(), os.userInfo().username, the current working directory, and the first 30 entries of process.env, then HTTPS-POSTs the JSON payload to a second hardcoded Burp Collaborator host (3nrgzlqwix6erldow0s0kttsojuai36s.oastify.com). Both endpoints are oastify.com out-of-band-application-security-testing infrastructure used for blind data exfiltration. The package name impersonates NASA's openmct ecosystem (the exfil path /nasa/couchrestore/ reinforces the lure), the package description falsely claims to be an AWS CDK SageMaker workflow, and the README contains the string 'Takeover By l0bo'. Installer harm is unconditional and fires before any user code runs.

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

3c1380885956f163ad3cb8a1d2cf1221fa8bcb39aa2bdf7dcc3df83ab5ce8056

4f246b80cd72ab384a5270f974631d20ebddac7ccac137434102dfdbfd0ea9db

ce8eff366d17efa64bf8605941d009d01cf7a24aaf011af30faec449fc4a2e28

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

Campaign

IN-MAL-2026-004232IN-MAL-2026-004235IN-MAL-2026-004234

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks openmct-couch-plugin-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