Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@welcome-onboarding-web/mobile-focus-account-beta-mergingnpm

Malicious code in @welcome-onboarding-web/mobile-focus-account-beta-merging (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5923
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @welcome-onboarding-web/mobile-focus-account-beta-merging

What this malware does

scripts/postinstall.js is heavily obfuscated (obfuscator.io with rotated base64-RC4 string array and a self-defending regex tamper check that infinite-loops on debuggers/beautifiers). On npm install, the postinstall hook walks up from process.cwd() to fingerprint the parent project, selects a remote URL based on os.platform() (linux/darwin/win32), fetches the response body via http(s).get into a Buffer, writes it to a file under os.tmpdir(), then spawns it via child_process.spawn(process.execPath, [tmpFile], {detached: true, stdio: 'ignore', env: {...process.env,...}}).unref() — a classic detached install-time remote code dropper that ships the installer's full environment to the spawned process. The package's library surface is non-functional (declared main dist/index.js only re-exports ../src/index.js, but no src/ directory ships in the tarball), and the publisher identity (welcome-onboarding-web.io with fabricated jira/docs/github/npm subdomains) does not correspond to a real organization. The package's only effect on install is execution of the obfuscated dropper.

Malicious versions

1 flagged
4.28.7

Indicators of compromise (SHA-256)

5587680c29332345c8dd87172c03e0ba20f858c968d16c5a6c34717b8e95bcf5

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @welcome-onboarding-web/mobile-focus-account-beta-merging (version 4.28.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @welcome-onboarding-web/mobile-focus-account-beta-merging across your stack and pipelines.

  2. If you installed it — respond

    Remove @welcome-onboarding-web/mobile-focus-account-beta-merging from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @welcome-onboarding-web/mobile-focus-account-beta-merging 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.

  4. How O3 protects you

    O3 blocks @welcome-onboarding-web/mobile-focus-account-beta-merging 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. @welcome-onboarding-web/mobile-focus-account-beta-merging on npm has been identified as a malicious package (version 4.28.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006830

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @welcome-onboarding-web/mobile-focus-account-beta-merging-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

@welcome-onboarding-web/mobile-focus-account-beta-merging (npm) malicious package — MAL-2026-5923 | O3 Security