Which versions of loading-sessions are malicious?

The following npm versions of loading-sessions are flagged malicious: 6.13.2. Treat any of these as compromised.

How do I remediate loading-sessions if I installed it?

loading-sessions is a typosquat — you almost certainly intended a legitimately-named package. Remove loading-sessions, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed loading-sessions — how do I know if it already compromised me?

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

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

Malicious package

loading-sessionsnpm

loading-sessions is a confirmed malicious npm package (MAL-2026-10471) that typosquats a legitimate package to trick installs (malicious version 6.13.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in loading-sessions (npm)

MAL-2026-10471

Immediate action

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

npm uninstall loading-sessions

What this malware does

Package name impersonates the pino logger (exports module.exports.pino, ships pino-style files lib/proto.js, lib/levels.js, lib/redaction.js, lib/multistream.js, lib/transport.js, copies pino keywords ['fast','logger','stream','json']). When the exported middleware is invoked, index.js spawns a detached node lib/caller.js child. lib/caller.js base64-decodes a hardcoded URL (https://api.jsonstorage.net/v1/json/2ef8c758-a96f-459e-b036-b3b90379a165/a179ea35-b962-4722-b3f1-e28316d1a44a) disguised as a DEV_API_KEY env-var fake, GETs the JSON document, and passes the response's data.cookie string to new Function.constructor('require', s) and invokes it with require. The fetched content is attacker-controlled and mutable, runs with full Node require access, retries up to 5 times, and is detached so failures are silent. Headers (x-secret-key) are also base64-decoded from masquerading env-var names. This is a classic remote-code dropper hidden behind a typosquat lure.

Malicious versions

1 flagged

6.13.2

Indicators of compromise (SHA-256)

ed919f49d3732fb5d4bd8b177022ed58d9c08b2cded5a6141e2da07c66966a94

2907d99272726cc1d10648311e8b9ae77b53164a89ab868a510dc1d6f1c4c11f

a1d8bcdcd684fcc154d56384b6a7779d786910d7133cf66534d0e270b090bb0d

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for loading-sessions (version 6.13.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging loading-sessions across your stack and pipelines.
If you installed it — respond
loading-sessions is a typosquat — you almost certainly intended a legitimately-named package. Remove loading-sessions, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If loading-sessions 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 loading-sessions 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. loading-sessions on npm has been identified as a malicious package (version 6.13.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010290RLMA-2026-05569RLUA-2026-06309

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks loading-sessions-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