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

@mohamed_nowisar/token3-checknpm

Advisory published Updated

@mohamed_nowisar/token3-check is a confirmed malicious npm package (MAL-2026-14135) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mohamed_nowisar/token3-check (npm)

MAL-2026-14135
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mohamed_nowisar/token3-check

What this malware does

The package registers preinstall, install, and postinstall lifecycle hooks that all execute beacon.js. On any npm install, beacon.js collects the installer's hostname (os.hostname()), username (os.userInfo().username), current working directory (process.cwd()), platform/arch, Node.js version, and a curated set of CI-detection environment variables (including YANDEX_CI, GITHUB_ACTIONS, GITLAB_CI, JENKINS_URL) and POSTs them via https.request to a hardcoded endpoint at https://webhook.site/3687e44a-4e97-43c4-84c9-e6c93d4b2fbc. The package self-describes as a dependency-confusion canary targeting the Yandex build pipeline, but installers do not opt in to the beacon and the destination is a third-party inspection endpoint controlled by the publisher. Internal build-system identity and CI fingerprints leaked this way enable follow-on dependency-confusion attacks against the exposed pipelines.

Malicious versions

1 flagged
0.0.1

Indicators of compromise (SHA-256)

10d463b1de43a90878da858dd595dadf43fcbbbb9d2e26cfd8b14ff6e0167457

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @mohamed_nowisar/token3-check (version 0.0.1).

  2. If you installed it — respond

    @mohamed_nowisar/token3-check 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.

  3. Did it already run?

    If @mohamed_nowisar/token3-check 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. @mohamed_nowisar/token3-check on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018179

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @mohamed_nowisar/token3-check-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
@mohamed_nowisar/token3-check (npm) malicious package — MAL-2026-14135 | O3 Security