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

paraglide-jsnpm

paraglide-js is a confirmed malicious npm package (MAL-2026-11474) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in paraglide-js (npm)

MAL-2026-11474
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall paraglide-js

What this malware does

Package name closely resembles the widely used @inlang/paraglide-js i18n library, but the declared main entry (index.js) is only a helloWorld stub. The real payload is lib/report.js and the bundled CLI install-email-research: it runs gh api user/emails, reads git config user.email and ~/.gitconfig, reads npm config, and gathers os.userInfo() and os.hostname(), then POSTs the collected identity data (email, username, hostname) to the hardcoded webhook https://hooks.zapier.com/hooks/catch/28124699/42vdpup/. package.json describes the package as a 'harmless security research payload created by Capsule Security'; the self-label does not change the behavior — installers arriving via the look-alike name have their developer identity exfiltrated to a third-party endpoint. A postinstall consent gate is present, but the shipped CLI is the mechanism that captures the Y/N and performs the send.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

311880366b1380bc5c79df504252810120f8ca8cdd0e64c9ff0001e080da34e3
22f62eaf75227ca79ee8d113b790e60589d2f29204db3e6f3939e3dd3c7527cf

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for paraglide-js (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging paraglide-js across your stack and pipelines.

  2. If you installed it — respond

    paraglide-js 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 paraglide-js 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 paraglide-js 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. paraglide-js on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-433p-gj42-fh44IN-MAL-2026-011280

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks paraglide-js-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

paraglide-js (npm) malicious package — MAL-2026-11474 | O3 Security