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

rtc-integration-frontend-sdknpm

Malicious code in rtc-integration-frontend-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10129
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rtc-integration-frontend-sdk

What this malware does

[email protected] registers a postinstall lifecycle hook ("postinstall": "node index.js") that fires automatically on npm install. index.js collects installer host reconnaissance — os.hostname(), userInfo().username, platform/arch, local network interface addresses, the public IP resolved via a call to https://api.ipify.org, the current working directory, and the package name — and POSTs the collected data to a hardcoded Discord webhook at discord.com/api/webhooks/. The package name and 99.9.0 version shape are consistent with a typosquat/version-bump lure; installing the package causes unconditional install-time exfiltration of host identifiers to an attacker-controlled endpoint.

Malicious versions

1 flagged
99.9.0

Indicators of compromise (SHA-256)

acfd49527fb8be1135feb424b68f6c46779ba146d8372d276eac1735770d6e5a

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 rtc-integration-frontend-sdk (version 99.9.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rtc-integration-frontend-sdk across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

IN-MAL-2026-009613

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rtc-integration-frontend-sdk-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
rtc-integration-frontend-sdk (npm) malicious package — MAL-2026-10129 | O3 Security