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

@mohamed_nowisar/depconf-canary-testnpm

@mohamed_nowisar/depconf-canary-test is a confirmed malicious npm package (MAL-2026-14134) 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/depconf-canary-test (npm)

MAL-2026-14134
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @mohamed_nowisar/depconf-canary-test

What this malware does

On npm install, the package's preinstall hook runs node beacon.js, which collects host identity (os.hostname(), os.userInfo().username, process.cwd(), platform, arch, Node version) and CI-detection environment variables (GITLAB_CI, GITHUB_ACTIONS, YANDEX_CI, and others) and POSTs them as JSON to the hardcoded endpoint https://webhook.site/3687e44a-4e97-43c4-84c9-e6c93d4b2fbc. The package name and self-description frame this as a dependency-confusion canary, but the beacon fires automatically on install without opt-in and sends installer-side data to an author-controlled webhook.site collector.

Malicious versions

1 flagged
0.0.1

Indicators of compromise (SHA-256)

078a8dc3351eb44ee9ff0d5992b9082b726d7fbce0152ae2d44595a9e279ef82

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @mohamed_nowisar/depconf-canary-test (version 0.0.1).

  2. If you installed it — respond

    @mohamed_nowisar/depconf-canary-test 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/depconf-canary-test 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/depconf-canary-test 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-018178

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @mohamed_nowisar/depconf-canary-test-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/depconf-canary-test (npm) malicious package — MAL-2026-14134 | O3 Security