Which versions of proton-account are malicious?

The following npm versions of proton-account are flagged malicious: 99.99.99, 99.99.999, 99.99.9999. Treat any of these as compromised.

How do I remediate proton-account if I installed it?

Remove proton-account 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.

I already installed proton-account — how do I know if it already compromised me?

If proton-account 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.

Is proton-account part of a known attack campaign?

Yes — proton-account is associated with the RLMA-2026-05235 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find proton-account across my projects, lockfiles, and CI pipelines?

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

Malicious package

proton-accountnpm

proton-account is a confirmed malicious npm package (MAL-2023-1273) that executes malicious code on install (malicious versions 99.99.99, 99.99.999, 99.99.9999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in proton-account (npm)

MAL-2023-1273

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall proton-account

What this malware does

The OpenSSF Package Analysis project identified 'proton-account' @ 99.99.999 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

3 flagged

99.99.9999.99.99999.99.9999

Indicators of compromise (SHA-256)

edfb8318aed91ce8eb51e269ae47766d501e4e03c1b95f4327570493b4b1379c

a3906f02579ee568a2dcd6f465246219fcae1864ff7fa0ad33cd80f1e0a74c4f

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for proton-account (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging proton-account across your stack and pipelines.
If you installed it — respond
Remove proton-account 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.
Did it already run?
If proton-account 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.
How O3 protects you
O3 blocks proton-account 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. proton-account on npm has been identified as a malicious package (versions 99.99.99, 99.99.999, 99.99.9999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05235

References

security.snyk.io

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks proton-account-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database