What does the @latlongid/location malware do?

@latlongid/location@1.0.1 declares `postinstall: node index.js` in package.json, so `index.js` runs automatically on every `npm install`. That script hex-encodes the installer's `os.hostname()` and embeds it as a subdomain of `dns.gl0b.xyz`, then invokes `dns.lookup` on the constructed name (e.g. `2d5bccee-...-h . .dns.gl0b.xyz`). The DNS query name itself carries the host identifier off the machine, so exfiltration succeeds regardless of resolution result. The scoped name and generic 'internal utility' metadata are consistent with a dependency-confusion reconnaissance beacon designed to enumerate reachable internal build environments.

Which versions of @latlongid/location are malicious?

The following npm versions of @latlongid/location are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @latlongid/location if I installed it?

@latlongid/location is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @latlongid/location — how do I know if it already compromised me?

If @latlongid/location 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 @latlongid/location part of a known attack campaign?

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

Malicious package

@latlongid/locationnpm

@latlongid/location is a confirmed malicious npm package (MAL-2026-12506) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @latlongid/location (npm)

MAL-2026-12506

Immediate action

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

npm uninstall @latlongid/location

What this malware does

@latlongid/[email protected] declares postinstall: node index.js in package.json, so index.js runs automatically on every npm install. That script hex-encodes the installer's os.hostname() and embeds it as a subdomain of dns.gl0b.xyz, then invokes dns.lookup on the constructed name (e.g. 2d5bccee-...-h<hex(hostname)>.<rand>.dns.gl0b.xyz). The DNS query name itself carries the host identifier off the machine, so exfiltration succeeds regardless of resolution result. The scoped name and generic 'internal utility' metadata are consistent with a dependency-confusion reconnaissance beacon designed to enumerate reachable internal build environments.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

134cf39570bebc6b10043353b9194b41e30da9b0f55147501ccc060bb32c7e8e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @latlongid/location (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @latlongid/location across your stack and pipelines.
If you installed it — respond
@latlongid/location is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @latlongid/location 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 @latlongid/location 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. @latlongid/location on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014933

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @latlongid/location-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database