Which versions of onboarding-respects-modal are malicious?

The following npm versions of onboarding-respects-modal are flagged malicious: 999.99.99. Treat any of these as compromised.

How do I remediate onboarding-respects-modal if I installed it?

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

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

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

Malicious package

onboarding-respects-modalnpm

Malicious code in onboarding-respects-modal (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6258

Immediate action

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

npm uninstall onboarding-respects-modal

What this malware does

onboarding-respects-modal is a dependency confusion proof-of-concept package published to the public npm registry by the account r0binak and self-labeled "Security research PoC - Dependency Confusion Hunter". It was published at the artificially high version 999.99.99, a floating-version bait used to outrank a private-registry package of the same name so that build pipelines preferring the highest available version resolve and install this public package instead. It belongs to the same r0binak dependency-confusion campaign as carousel-controller-mixin (MAL-2026-5856) and setka-editor (MAL-2026-5859). Packages in this campaign declare both preinstall and postinstall hooks that run callback.js on every npm install; the script collects installer identity and environment data (username, uid/gid, hostname, homedir, cwd, platform, Node version, local network interfaces, and the external IP via api.ipify.org) and probes for CI/cloud credential environment variables (AWS_ACCESS_KEY_ID, GITHUB_TOKEN, NPM_TOKEN, DOCKER_PASSWORD) plus GitHub Actions context. The collected data is exfiltrated to a hardcoded Discord webhook and via a DNS side-channel (base64-encoded host data prepended as a subdomain and resolved with dns.resolve()) to defeat egress HTTP filtering on CI networks. Regardless of the stated research intent, install-time exfiltration of host data and credential-presence flags is harmful to any pipeline that resolves this name.

Package name 'onboarding-respects-modal' published at version 999.99.99 to win dependency resolution against a private internal package of the same name. package.json declares both preinstall and postinstall lifecycle hooks that execute callback.js, which collects the installer's user info (username, uid/gid, homedir, shell), hostname, local and external IPs (via https://api.ipify.org), CI detection, and the entire process.env object with no redaction (the source comments explicitly note no masking), then POSTs the JSON payload over plain HTTP to the hardcoded bare-IP endpoint http://132.243.20.244:8000/api/collect. Any installer pulling this package — particularly in CI — leaks every secret in the job environment (GITHUB_TOKEN, NPM_TOKEN, AWS_*, etc.) to the attacker-controlled host. The README's 'security research PoC' label does not change installer impact: the package is live on the public registry and the exfiltration fires unconditionally on npm install.

Malicious versions

1 flagged

999.99.99

Indicators of compromise (SHA-256)

c87cbbbfaff388bddc7f9811089bcfaf952a54374561768196669951b1da0ffd

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

Campaign

IN-MAL-2026-007103

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks onboarding-respects-modal-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