Which versions of jstoauto are malicious?

The following npm versions of jstoauto are flagged malicious: 5.1.0. Treat any of these as compromised.

How do I remediate jstoauto if I installed it?

Remove jstoauto 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 jstoauto — how do I know if it already compromised me?

If jstoauto 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 jstoauto part of a known attack campaign?

Yes — jstoauto is associated with the RLMA-2025-06381, RLUA-2026-01382 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 jstoauto 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 jstoauto (version 5.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jstoauto across your stack and pipelines.

Malicious package

jstoautonpm

Malicious code in jstoauto (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192815

Immediate action

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

npm uninstall jstoauto

What this malware does

The package jstoauto was found to contain malicious code.

Malicious versions

1 flagged

5.1.0

Indicators of compromise (SHA-256)

642a01a302912c96e057f43ae99c70a8f275f6213be542f96b102cc97d59f808

4199f4ea506d7dd6896da26d3a93ff99b02fb665d1ba8752d18b904325bb649b

77dc7b3648d9832594307037f858224f8fbca4f22e6c145f82a49db3bb7e8aaa

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 jstoauto (version 5.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jstoauto across your stack and pipelines.
If you installed it — respond
Remove jstoauto 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 jstoauto 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 jstoauto 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. jstoauto on npm has been identified as a malicious package (version 5.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06381RLUA-2026-01382

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks jstoauto-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