Which versions of remote_session_elements are malicious?

The following npm versions of remote_session_elements are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate remote_session_elements if I installed it?

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

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

Yes — remote_session_elements is associated with the IN-MAL-2026-014842 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 remote_session_elements 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 remote_session_elements (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging remote_session_elements across your stack and pipelines.

Malicious package

remote_session_elementsnpm

remote_session_elements is a confirmed malicious npm package (MAL-2026-12427) that executes malicious code on install (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in remote_session_elements (npm)

MAL-2026-12427

Immediate action

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

npm uninstall remote_session_elements

What this malware does

Package version 9999.0.0 is published with placeholder metadata ("Shared utility helpers.", no author) — the canonical shape of a dependency-confusion squat designed to override an internal package of the same name during resolution. On npm install, the scripts.preinstall hook runs node callback.js, which reads os.hostname(), os.userInfo().username, the current working directory, the configured npm registry, and CI-provided repository identifiers (e.g. process.env.GITHUB_REPOSITORY) and sends them via HTTP GET to http://75.119.137.232:31337/depconfuse?pkg=..., a hardcoded bare-IP endpoint over cleartext HTTP. This provides an external operator with the internal package name, host identity, and originating CI repository slug of every environment where the squat is installed — reconnaissance for further dependency-confusion attacks against the victim's internal package namespace.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

3a2127d34a7d033e96e00a679891716647f0a00f7590ad738b43d985e83dda69

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

Campaign

IN-MAL-2026-014842

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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