Which versions of vybscan-testbed-inert-postinstall are malicious?

The following npm versions of vybscan-testbed-inert-postinstall are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate vybscan-testbed-inert-postinstall if I installed it?

vybscan-testbed-inert-postinstall 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 vybscan-testbed-inert-postinstall — how do I know if it already compromised me?

If vybscan-testbed-inert-postinstall 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 vybscan-testbed-inert-postinstall part of a known attack campaign?

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

Malicious package

vybscan-testbed-inert-postinstallnpm

Malicious code in vybscan-testbed-inert-postinstall (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10078

Immediate action

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

npm uninstall vybscan-testbed-inert-postinstall

What this malware does

package.json declares a postinstall lifecycle script that runs id and reads the process environment, piping the collected host identity and environment variables to a remote endpoint via curl. This fires automatically on npm install without user interaction, causing the installer's environment variables (which routinely contain credentials, tokens, and API keys) and user/host identity to be transmitted off-host to an attacker-controlled destination.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

f4e6f35e49b7701bb75a88eb63fcf918c389272d5282093c8422d9e1f388dd38

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

Campaign

IN-MAL-2026-009213

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks vybscan-testbed-inert-postinstall-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