Which versions of lil-swisgom-hlepers are malicious?

The following npm versions of lil-swisgom-hlepers are flagged malicious: 49.9.9. Treat any of these as compromised.

How do I remediate lil-swisgom-hlepers if I installed it?

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

I already installed lil-swisgom-hlepers — how do I know if it already compromised me?

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

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

Malicious package

lil-swisgom-hlepersnpm

lil-swisgom-hlepers is a confirmed malicious npm package (MAL-2026-15689) that typosquats a legitimate package to trick installs (malicious version 49.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lil-swisgom-hlepers (npm)

MAL-2026-15689

Immediate action

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

npm uninstall lil-swisgom-hlepers

What this malware does

package.json declares a dependency lil-swisgom-hlepers-core whose version specifier is a direct tarball URL on a third-party host (https://registry.grivy-packages.com/lil-swisgom-hlepers-core/-/lil-swisgom-hlepers-core-49.9.9.tgz) rather than a version resolved from the npm registry. On npm install, npm downloads and installs the arbitrary tarball from that host into the installer's dependency tree, bypassing npm registry review and scanning; any code the tarball ships (including install lifecycle scripts and module-load side effects) then runs on the installer's machine. The package name itself is a misspelling (hlepers for helpers), consistent with a typosquat lure funneling installers into pulling attacker-hosted tarball content.

Malicious versions

1 flagged

49.9.9

Indicators of compromise (SHA-256)

48bf599d7e976dd083e7ce4db9b65a513292caf083fababbf12ef96014eeec8b

75aeaaa8ef6f56423bf517d9ff21cfed3a682701f306103f068b948e330f03db

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

Campaign

RLMA-2026-06305IN-MAL-2026-019395

References

npmjs.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks lil-swisgom-hlepers-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