May no longer be working? about inspy HOT 11 CLOSED

Hey guys, thanks for the heads up on this! Seems like LinkedIn is changing up their schemes again. Not going to lie here, I am going to be pretty busy for the next couple of weeks and would really appreciate any help fixing this. If you guys can give it a shot, and send it back my way, I'll test it and merge it. Thanks in advance!

from inspy.

Hey everyone, working on InSpy v3 at the moment. You can expect HTTP 999 errors, these are custom LinkedIn errors that can't be bypassed despite UA randomization. The next version should be released within a couple of days but for now try randomizing the UA and slowing down requests.

from inspy.

+1 momoisacat's comment. Loaded OK and script ran, but even when repeating the Microsoft example I received a '0 Employees identified' response.
Either things have been going badly recently in Redland, or there's an issue with the Script or LinkedIn are blocking it

from inspy.

Same here. My hunch is that LinkedIn changed the format of the responses.

from inspy.

So they definitely are throttling things. I know I'm late to the party here but it let me do 1 search and get results then not again. I'll try later to see if it'll let me again.

edit; If anyone is wondering you can use the script like.. Once every so often to get a big dump but it won't work again for a while. Just in case anyone needed this for a.. specific use case.

from inspy.

It worked the first run for a partial scape then I started getting 999 errors. I`m going to guess linkedin see's the generic user-agent string and a quick crawl, then just blacklists the ip+user-agent. Adding in a custom user-agent flag or randomizing the user-agent along with a timing option would likely help.

2017-12-14 19:33:50,182 DEBUG - "GET /title/administration-at- HTTP/1.1" 999 1461
2017-12-14 19:33:50,188 INFO - Starting new HTTPS connection (1): www.linkedin.com
2017-12-14 19:33:51,413 DEBUG - "GET /title/engineering-at- HTTP/1.1" 999 1461
2017-12-14 19:33:51,418 INFO - Starting new HTTPS connection (1): www.linkedin.com
2017-12-14 19:33:52,254 DEBUG - "GET /title/it-at- HTTP/1.1" 999 1461

from inspy.

any resolution to this issue?

from inspy.

--techspy seems to have an issue without errors. It finishes in about 1s with 0 jobs identified. --empspy however seems to crawl and return results just fine

from inspy.

Hi I have installed Inspy

But I cannot found --empspy and --techspy after the installation

root@kali:# apt install inspy
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
inspy
0 upgraded, 1 newly installed, 0 to remove and 589 not upgraded.
Need to get 9,224 B of archives.
After this operation, 46.1 kB of additional disk space will be used.
Get:1 http://kali.download/kali kali-rolling/main amd64 inspy all 3.0.0-0kali2 [9,224 B]
Fetched 9,224 B in 9s (1,063 B/s)
Selecting previously unselected package inspy.
(Reading database ... 344575 files and directories currently installed.)
Preparing to unpack .../inspy_3.0.0-0kali2_all.deb ...
Unpacking inspy (3.0.0-0kali2) ...
Setting up inspy (3.0.0-0kali2) ...
root@kali:# inspy -h
usage: inspy [-h] [-v] [--domain DOMAIN] [--email EMAIL] [--titles [file]]
[--html file] [--csv file] [--json file] [--xml file]
company

InSpy - A LinkedIn enumeration tool by Jonathan Broche (@leapsecurity)

positional arguments:
company Company name to use for tasks.

optional arguments:
-h, --help show this help message and exit
-v, --version show program's version number and exit
--domain DOMAIN Company domain to use for searching.
--email EMAIL Email format to create email addresses with. [Accepted
Formats: [email protected], [email protected],
[email protected], [email protected], [email protected],
[email protected], [email protected], [email protected]]
--titles [file] Discover employees by title and/or department. Titles and
departments are imported from a new line delimited file.
[Default: title-list-small.txt]

Output Options:
--html file Print results in HTML file.
--csv file Print results in CSV format.
--json file Print results in JSON.
--xml file Print results in XML.
root@kali:~#

from inspy.

same here

from inspy.

Any updates on this issue? not able to work with inspy 3.0

from inspy.